CIG Mapping - How to do Mapping for Extrinsic with Sublevel

[nikotadena]

Hi Experts,

We have a requirement to include PO Serviced Amount while sending the PO OrderRequest (ECC>CIG>AN) transaction for Legacy POs. Our SR support has advised that the following should be included on the iDOC (sent from ERP) and on CIG we map these fields to Extrinsic fields as sampled below. However, I am having problems implementing the sample since there is sort of a 'sub' extrinsic segment required - in this case the "Money" section. I am able to implement straightforward Extrinsic mapping (map an iDOC field to Extrinsic, assign a value @name then add source condition) set up only - but no idea yet for this Extrinsic with sub-level. Would you share a guide (if this is possible) on how to implement this via CIG mapping? If not possible, are there any alternatives?

Sample from SR Engr:

<Extrinsic name="AribaNetwork.LegacyPOServicedAmount">

<Money currency="USD">20000</Money>

</Extrinsic>

[Tanua_Lourenco1]

Hi Niko,

Where you able to map the extrinsic of type money to the required field?

I'm having the same issue and even when I try to point at the ExtrinsicName/Money no value is filled out in the destination.

Thanks in advance,

Best regards,

Tânia

[adrian_fernandez4]

Hi Niko.

What do you meant when you say "sublevel"?

Normally, you have the extrinsic and the "name" argument. So, in extrinsic field you must map your value from ECC, you can implement any condition to this field, and in the argument "name" you must set your field name, for example "AribaNetwork.LegacyPOServicedAmount".

See the screenshot. If you have any other different structure, please share it to fix the problem.

Regards.

Adrián.

[nikotadena]

sampleextendedextrinsic.png

Hi Adrian,

Here it is.

[adrian_fernandez4]

Hi Niko.

Well, I had never seen this configuration. Usually, these extrinsics have entrinsic tag and @name argument.

Can you check if you have any extrinsic structure like this inside the mapping configuration in your PO scenario? Maybe, the engineers added it inside the mapping.

Also, review the "Mapping specs" of PO into "Resources" tag. Open the file and look into if this extension exists.

Regards.