Purchase Order IDoc

[Former Member]

Hi together,

we are working on the purchase integration between ByDesign and SAP ERP. Concerning this matter I have 4 questions regarding the purchase idoc:

- Is it possible to map a custom specific field to an idoc field?

- Is it possible to map two concatenated custom specific fields into an Idoc field

- In the purchase idoc the Unit of Measurement is EA but SAP ERP requires ISO Code (in this case PCE). Is it possible to change this?

- Is there a way to extend the idoc structure?

Thanks a lot in advance for your help.

Best regards,
Constantin

[knutheusermann · Accepted solution]

Hello Constantin,

unfortunately we don't support Purchase Order IDoc extensibility in ByD today, but your scenario could be solved using B2B (Business to Business) or purchase order APIs (A2X services):

1. Use B2B communication scenario "Purchase Order Integration" as purchase order output channel and utilize some middleware (e.g. SAP HCI) to map the B2B messages to ECC IDoc interfaces.
2. Use the standard IDoc-Integration as is (without extension fields) as ByD output channel and pull additional ByD purchase order information using ByD web services QueryPurchaseOrderQueryIn and ManagePurchaseOrderIn. The pull-mechanism can be build on some middleware or embedded in the ECC ALE infrastructure.

Both approaches enable you to transfer most purchase order information incl. extension fields and additional IDoc segments from ByD to ECC.

Is it possible to map two concatenated custom specific fields into an IDoc field?

You can create an extension field using SAP Cloud Applications Studio and fill the field on the purchase order event "after modify" or "before save"; then you can transfer the concatenated information in the extension field to ECC as described above.

In the purchase order IDoc the Unit of Measurement is EA but SAP ERP requires unit code PCE. Is it possible to change this?

The ByD code list for Unit of Measures is defined along the Codes for Units of Measure Used in International Trade as specified in UN/CEFACT
Recommendation #20. This code list incl. code "EA - A unit of count defining the number of items regarded as separate units" only.

You can enhance the code list for units of measurements using the ByD business configuration activity "Quantities and Units of Measure" by unit codes in the Z-namespace. Unfortunately this means that the unit code PCE cannot be added.

A code mapping EA to PCE (code list mapping) during the ByD purchase order outbound is not yet supported as well.

However, following one of the two approaches above a code mapping EA to PCE can be solved as part of the middleware mapping or ECC inbound.

A third option (which is very likely not feasible for most companies) would be to enhance the ECC unit of measure code list to support the unit code EA as well.

Best regards,

Knut

[knutheusermann · Accepted solution]

Hello Constantin,

Stefan Möller wrote a blog in SCN which might be interesting for you as well in this context:

Best regards,

Knut