Loading.....

Definition

The Create Internal Request service operation is a request to create or confirm the creation of an internal request. This action creates a shopping cart.

Business Context and Use

Purchasers can use the Create Internal Request inbound service operation to create internal requests (shopping carts). This service operation represents the SRM shopping cart.

Error Handling

Messages can be rejected for either technical or business reasons. The log node in the response message signature provides detailed information about why messages have been rejected.

Integration

Constraints

The following constraints apply to the Create Internal Request service operation:

Signature

Hierarchies are not supported, therefore the  ParentID value can only be 0.

Product Definition

Freetext Product:

Internal Product:

• Item – Product – Category : this field is mandatory, and it must match the Product Category as specified in SRM
• Item – Product – Category-schemeID : this attribute is mandatory, and it takes the scheme of category identification, that is, ProductCategoryID
• Item – Product – Category-schemeAgencyID : this attribute is mandatory, and it takes the ID of the logical system
• Item – Product – Product – Note : this field is mandatory, and it must match the Product Description as specified in SRM
• Item – Product – Product – TypeCode : this field is mandatory, and it must match the Product Type as specified in SRM
• Item – Product – Product – InternalID : this field is mandatory, and it must match the Product ID as specified in SRM according to the schemeID attribute
• Item – Product –  Product – InternalID – SchemeID : this attribute is mandatory, and it takes the scheme of product identification, that is, ProductID
• Item – Product –  Product – InternalID – SchemeID – SchemeAgencyID : this attribute is mandatory, and it takes the ID of the logical system
• Item – Quantity – unitCode : the Quantity field and unitCode  attribute are mandatory, and unitCode  must match the product’s unit of measure
• Item – NetUnitPrice – unitCode : the NetUnitPrice  field is optional, but if it is specified, then the unitCode attribute is mandatory, and it must match the product’s unit of measure
• Item AccountingCodingBlockAssignment – Quantity – unitCode : the  AccountingCodingBlockAssignment  field is optional, but if it is given with the Quantity field, then the unitCode attribute is mandatory, and it must match the product’s unit of measure

Limit Item:

• Item – Product – Category : this field is mandatory, and it must match the Product Category as specified in SRM
• Item – Product – Category-schemeID : this attribute is mandatory, and it takes the scheme of category identification, that is, ProductCategoryID
• Item – Product – Category-schemeAgencyID : this attribute is mandatory, and it takes the ID of the logical system
• Item – Product – Category : this field is mandatory
• Item – Product – Product – Note : this field is mandatory
• Item – Product – Product – InternalID : this field must not be submitted
• Item – ProcurementCostUpperLimit : this field is mandatory

Catalogue Reference:

This value is optional; the product data is not validated against the catalog.

Other Constraints

• If neither the Requestor nor Recipient value is specified, the logon user name is assigned to both.
• If a Requestor is specified, but a Recipient is not specified, the Requestor is assigned to be the Recipient .
• The following BTDParty fields are evaluated:
• InternalID
• Address – OrganizationFormattedName
• Address – PersonName
• Address – PhysicalAddress
• Address – Communication
• With the exception of Limit Items , only one delivery date can be specified.  The system adopts this date according to the following sequence: DeliveryDatePeriod – EndDate , DeliveryDatePeriod – StartDate , (default) current date .
• Limit Item supports only Invoice and Confirmation .

ES Bundles

This operation is contained in the following ES Bundles:

• Resource and Supply Chain Planning for Healthcare Providers