Skip to Content
0
Jun 26, 2018 at 02:03 PM

Changing from a standard idoc mapping to adding a new Z version of the idoc in the mapping

128 Views

So i've got a mapping that worked, its between a idoc invoic, and maps to a customer format. The customer wanted some additional fields so we extended the idoc. We now have a z version of that idoc. I thought i'd be able copy the mapping and then drag and drop the extended idoc into the source location in the mapping - i did this, checked out the mapping and all these fields remained mapped - too good to be true i thought.

As soon as i started to check a few of the mappings by checking their queues, i was getting NULL back, so its like its not reading the field, there is definitely data in the test screen so it should return something. As per image 1.1.png


There is the question of the outstanding, new z segments which i've requested from the customer as to how they should be mapped but the mapping fails way before that segment, which is at the bottom of the xsd and returns an error:

Cannot create target element /C_UNTO/S_STX/ns0:INVFILTO9/D_CODE. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD
See error logs for details

But as you can see in image 2 d_code is very much there, has data , mappings exist but doesnt have any data coming through.2.png

AS a quick test, ive tried removing the a fields mapping and reapplying it, i still get the "Null" result.

Would it be that i should reload the entire target document as well, then i might have to remap the entire document again?

Thanks for your input.

Attachments

1.png (22.2 kB)
2.png (56.4 kB)