[doc issue] No reference for message mapping

[miguelesteva]

Issue description

It is not clear how the message mapping was done. It should contain the source and target message. All of a sudden, there's PurchaseOrder and Quantity in the target message.

The XSD for Product only contains the following fields.

<Products>
    <Product>
      <Category>Beamers</Category>
      <WeightUnit>KG</WeightUnit>
      <ProductId>HT-6102</ProductId>
      <DimensionUnit>m</DimensionUnit>
      <DimensionHeight>0.2300</DimensionHeight>
      <Weight>2.500</Weight>
      <Name>Beam Breaker B-3</Name>
      <ShortDescription>2500 ANSI-Lumen, max.12,3Meter, 800 Pixel, 600 Pixel</ShortDescription>
      <CurrencyCode>EUR</CurrencyCode>
      <DimensionWidth>0.3040</DimensionWidth>
      <SupplierId>100000043</SupplierId>
      <LongDescription>2500 ANSI-Lumen, max.12,3Meter, 800 Pixel, 600 Pixel</LongDescription>
      <Price>889.000</Price>
      <CategoryName>Beamers</CategoryName>
      <PictureUrl>HT-6102.jpg</PictureUrl>
      <DimensionDepth>0.2310</DimensionDepth>
      <QuantityUnit>EA</QuantityUnit>
    </Product>
  </Products>

Feedback Type (Optional)

content gaps

Page Title on SAP Help Portal (prefilled)

Access Header and Properties in Message Mapping

Page URL on SAP Help Portal (prefilled)

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/access-header-and-properties-in-message-mapping?q=orderid

[SrutiSagaram]

Hi @miguelesteva
Thank you for your feedback. We will check and get back.

[peasantsboot]

@miguelesteva we do ship sample integration flows for almost all design guidelines, you can find the definition of the mapping here: https://hub.sap.com/integrationflow/ModelingBasics_AccessHeaderAndPropertiesInMessageMapping/resources/mapping/MapToOrder.mmap
By the way, I just figured that this guideline is not up to date, you don't need to create own scripts to access headers and properties any more, the mapping tool supports functions to access headers and properties out of the box.

Alex