Issue with Prod Order Yield Confirmation - Missing serial number

[harsh-ctrl]

Hi experts,

I am facing an issue with a part of the request payload missing - " <ns2:serialNumber>17</ns2:serialNumber> " for the transaction " Production Order Yield Confirmation ", due to which this transaction is failing in the scenario explained below-

Scenario 1: Orders released on MAT 83 which has a serial profile(in ERP) on:

• If orders are processed on DM without making modifications to SFC, ie without serialization the payload is (Notable lines - 22 to 26)- 

<ns2:yieldConfirmationRequest xmlns:ns2="http://sap.com/xi/ME/erpcon">
    <ns2:messageID>3690f8b3-2f45-49c9-92bd-1cefd154d272</ns2:messageID>
    <ns2:plant>0001</ns2:plant>
    <ns2:orderNumber>1001579</ns2:orderNumber>
    <ns2:operation>
        <ns2:operation>1001579-0-0030</ns2:operation>
        <ns2:version>ERP001</ns2:version>
    </ns2:operation>
    <ns2:routing>
        <ns2:routing>1001579</ns2:routing>
        <ns2:version>ERP001</ns2:version>
        <ns2:routerType>SHOP_ORDER</ns2:routerType>
    </ns2:routing>
    <ns2:material>
        <ns2:material>000000000000000083</ns2:material>
        <ns2:version>ERP001</ns2:version>
    </ns2:material>
    <ns2:sequence>not_defined</ns2:sequence>
    <ns2:stepId>0030</ns2:stepId>
    <ns2:reportingStep>0030</ns2:reportingStep>
    <ns2:productionVersion>PV1</ns2:productionVersion>
    <ns2:wipIdentifier>
        <ns2:sfc>000000000000000083-17</ns2:sfc>
        <ns2:serialNumber>17</ns2:serialNumber>
        <ns2:quantity>1.000000</ns2:quantity>
    </ns2:wipIdentifier>
    <ns2:storageLocation>0002</ns2:storageLocation>
    <ns2:batchData>
        <ns2:batchNumber>
        </ns2:batchNumber>
        <ns2:isLastReportingStep>true</ns2:isLastReportingStep>
    </ns2:batchData>
    <ns2:unitOfMeasure>EA</ns2:unitOfMeasure>
    <ns2:erpComponentsOption>ONLY_NON_BACKFLUSHED</ns2:erpComponentsOption>
    <ns2:rework>false</ns2:rework>
    <ns2:isEwmIntegrationActive>false</ns2:isEwmIntegrationActive>
    <ns2:disableGoodsReceipt>false</ns2:disableGoodsReceipt>
    <ns2:startDateTime>2024-06-04T06:13:17.562Z</ns2:startDateTime>
    <ns2:completeDateTime>2024-06-04T06:13:31.130Z</ns2:completeDateTime>
    <ns2:workCenter>DMC-WC</ns2:workCenter>
    <ns2:enteredByExternalUser>harsh@incture.com</ns2:enteredByExternalUser>
</ns2:yieldConfirmationRequest>

• If orders are processed on DM after changing the SFC no, ie using serialization, the payload is(Notable lines 22 to 25) -

<ns2:yieldConfirmationRequest xmlns:ns2="http://sap.com/xi/ME/erpcon">
    <ns2:messageID>266836ef-8298-49ee-8d13-a54a0a548a40</ns2:messageID>
    <ns2:plant>0001</ns2:plant>
    <ns2:orderNumber>1001562</ns2:orderNumber>
    <ns2:operation>
        <ns2:operation>1001562-0-0030</ns2:operation>
        <ns2:version>ERP001</ns2:version>
    </ns2:operation>
    <ns2:routing>
        <ns2:routing>1001562</ns2:routing>
        <ns2:version>ERP001</ns2:version>
        <ns2:routerType>SHOP_ORDER</ns2:routerType>
    </ns2:routing>
    <ns2:material>
        <ns2:material>000000000000000083</ns2:material>
        <ns2:version>ERP001</ns2:version>
    </ns2:material>
    <ns2:sequence>not_defined</ns2:sequence>
    <ns2:stepId>0030</ns2:stepId>
    <ns2:reportingStep>0030</ns2:reportingStep>
    <ns2:productionVersion>PV1</ns2:productionVersion>
    <ns2:wipIdentifier>
        <ns2:sfc>MA1CH2F57B1234583</ns2:sfc>
        <ns2:quantity>1.000000</ns2:quantity>
    </ns2:wipIdentifier>
    <ns2:storageLocation>0002</ns2:storageLocation>
    <ns2:batchData>
        <ns2:batchNumber>
        </ns2:batchNumber>
        <ns2:isLastReportingStep>true</ns2:isLastReportingStep>
    </ns2:batchData>
    <ns2:unitOfMeasure>EA</ns2:unitOfMeasure>
    <ns2:erpComponentsOption>ONLY_NON_BACKFLUSHED</ns2:erpComponentsOption>
    <ns2:rework>false</ns2:rework>
    <ns2:isEwmIntegrationActive>false</ns2:isEwmIntegrationActive>
    <ns2:disableGoodsReceipt>false</ns2:disableGoodsReceipt>
    <ns2:startDateTime>2024-06-04T05:53:55.368Z</ns2:startDateTime>
    <ns2:completeDateTime>2024-06-04T05:54:06.749Z</ns2:completeDateTime>
    <ns2:workCenter>DMC-WC</ns2:workCenter>
    <ns2:enteredByExternalUser>harsh@incture.com</ns2:enteredByExternalUser>
</ns2:yieldConfirmationRequest>

KEY DIFFERENCE: The payload <ns2:serialNumber> is being skipped when we are serializing SFC in the above scenario. This resulted in the failure of this transaction with the following error - 

QUESTION: Is this happening due to any missing configuration or not I'm unable to identify it. Can you please help on this matter? 

Scenario 2: Orders released on MAT 23 which doesn't have a serial profile(in ERP) on:

In this case, the transaction for " Production Order Yield Confirmation " is not failing and sync is happening irrespective of whether SFC is being serialized or not.

Please let me know if we are missing something or is there any additional config that may be needed for this scenario. Any help will be valuable.

Thanks & Regards,
Harsh.

SAP Digital Manufacturing 

[ManoelCosta · Accepted solution]

Hi,
This seems to be working as designed at the moment. Once you explicitly (Re-)Serialize a SFC, DM is no longer referencing the original ERP Serial Number in the yield confirmation. If you have different requirements, please put an influence request.
Br,
Manoel