SAP SRM PunchOut e1474363733384
The full list of SAP SRM PunchOut Call-Up Parameters explained:
This post will explain the different return or Call-up Parameters from an External Punch Out
Table of Contents
Up to SAP Open Catalog Interface, thhe naming convention for the fields in the OCI is as follows:
NEW_ITEM-[]. The field type is always CHAR.
Here the Full list of SAP SRM PunchOut Call-Up Parameters returned when you check out from PunchOut Catalog.
| Field-name | Length | Description |
|---|---|---|
| NEW_ITEM-DESCRIPTION[n] | 40 | Description of the item |
| NEW_ITEM-MATNR[n] | 40 | SRM product number of the item |
| NEW_ITEM-QUANTITY[n] | 15 | Item quantity (1.) |
| NEW_ITEM-UNIT[n] | 3 | Quantity unit for item quantity (3.) |
| NEW_ITEM-PRICE[n] | 15 | Price of an item per price unit (1.) |
| NEW_ITEM-CURRENCY[n] | 5 | Item currency (3.) |
| NEW_ITEM-PRICEUNIT[n] | 5 | Price unit of the item (if empty 1 is used)(2.) |
| NEW_ITEM-LEADTIME[n] | 5 | Delivery time of the item in days (2.) |
| NEW_ITEM-LONGTEXT_n:132[] | ? | Long text for the item (4.) |
| NEW_ITEM-VENDOR[n] | 10 | SRM vendor number (business partner) for the item |
| NEW_ITEM-VENDORMAT[n] | 40 | Vendor product number for the item |
| NEW_ITEM-MANUFACTCODE[n] | 10 | SRM manufacturer number of the item |
| NEW_ITEM-MANUFACTMAT[n] | 40 | Item?s manufacturer part number |
| NEW_ITEM-MATGROUP[n] | 10 | SRM material group for the item |
| NEW_ITEM-SERVICE[n] | 1 | Flag: the item is a service. |
| NEW_ITEM-CONTRACT[n] | 10 | SRM contract to which the item refers |
| NEW_ITEM-CONTRACT_ITEM[n] | 5 | Item within the SRM contract |
| NEW_ITEM-EXT_QUOTE_ID[n] | 35 | Number of an external bid for this item (as reference for a subsequent purchase order) |
| NEW_ITEM-EXT_QUOTE_ITEM[n] | 10 | Item of external bid |
| NEW_ITEM-EXT_PRODUCT_ID[n] | 40 | Unique database key for this item in the catalog |
| NEW_ITEM-ATTACHMENT[n] 255 | URL | of the attachment (the attachment must be accessible for downloading under this URL) |
| NEW_ITEMATTACHMENT_TITLE[n] | 255 | Title of the attachment (if this is empty thefile name from the URL above is used) |
| NEW_ITEMATTACHMENT_PURPOSE[n] | 1 | Purpose of the attachment. C corresponds here to configuration. |
| NEW_ITEMEXT_SCHEMA_TYPE[n] | 10 | Name of a schema via which it was imported in the SRM Server |
| NEW_ITEMEXT_CATEGORY_ID[n] | 60 | Unique key for an external category from the schema above independent of the version of the schema |
| NEW_ITEM-EXT_CATEGORY[n] | 40 | Unique key for an external category from the schema above dependent on the version of the schema |
| NEW_ITEM-SLD_SYS_NAME[n] | 60 | Name of a system in the System Landscape Directory (SLD) |
The OCI interface has also 5 fields that used to send custom data between the Catalog and the SRM. Note that these fields are on Item’s level.
The list of User-Defined Field
| Field-name | Length | Description |
|---|---|---|
| NEW_ITEM-CUST_FIELD1[n] | 10 | User-defined field |
| NEW_ITEM-CUST_FIELD2[n] | 10 | User-defined field |
| NEW_ITEM-CUST_FIELD3[n] | 10 | User-defined field |
| NEW_ITEM-CUST_FIELD4[n] | 20 | User-defined field |
| NEW_ITEM-CUST_FIELD5[n] | 50 | User-defined field |
The Only Mandatory fields to be filled
Other fields are required depending on conditions:
If you want to extend the standard fields for the SAP SRM PunchOut Call-Up Parameters, you have 2 alternatives
These fields have no fixed semantics in the OCI and this means that you can transfer any contents in order to then evaluate them in BAdI BBP_CATALOG_TRANSFER. In Releases prior to SAP Enterprise Buyer 3.0 it is not possible to transfer these fields directly to the shopping cart item. As of SAP Enterprise Buyer 3.0, it is possible to include these fields (without the prefix NEW_ITEM-) in the customer-specific using the Include CI_BBP_ITEM_SC; the contents are then automatically forwarded to the shopping cart and saved with it.
This customer-specific Include is also available as of SAP Enterprise Buyer 3.0; it allows you to extend the OCI generically. All fields that are created in the Include can then be transferred by the catalog as NEW_ITEM-[n]. The fields are also available in the BAdI BBP_CATALOG_TRANSFER. If the fields are also to be available in the shopping cart and are to be saved, they must also be created in the Include CI_BBP_ITEM_SC
Find more detail on?SAP Open Catalog Interface (OCI) Specification
SAP ISU Tables for Technical master data, for Billing Master Data, Billing and invoicing Tables?…
SAP Fiori 3 UX and Design of SAP Fiori Apps for SAP S/4HANA, SAP TechEd…
Dunning is the business practice of informing a customer of past due payment. Dunning letters…
SAP AP Tcodes & SAP AR Tcodes: House Banks Tcodes, Advance Payments or Down Payments,…
What are the main SAP Payment Terms Tables ? What are the related Tables in…
Work center consists of master data related to routing of products. It contains data related…