Issue with DataHub Deployment: PayerID Not Displaying in Production

[mukulsahu7046]

Description:

I am experiencing an issue with the DataHub configuration when deploying the jar in the Production environment. Below is a detailed explanation of the problem:

1. UAT Environment:

   • When I deployed the jar in the UAT environment, everything worked perfectly.
   • The PayerID attribute was correctly displayed based on the configuration.

   • Production Environment:

     • After deploying the same jar in the Production environment, the PayerID is not displaying.

     • Jar Comparison:

       • I have compared the jars deployed in both UAT and Production environments, and they are identical.

         Configuration Details:

         Raw:

         <item>
         <type>CanonicalPartyRelationshipSales</type>
         <description>Canonical representation of a relationship between two parties</description>
         <attributes>
         <attribute>
         <name>relationshipTypeCP</name>
         <transformations>
         <transformation>
         <rawSource>RawDEBMAS</rawSource>
         <expression>E1KNA1M-E1KNVVM-E1KNVPM-PARVW</expression>
         </transformation>
         </transformations>
         </attribute>
         <attribute>
         <name>businessCustomerNumber</name>
         <transformations>
         <transformation>
         <rawSource>RawDEBMAS</rawSource>
         <expression>E1KNA1M-E1KNVVM-E1KNVPM-KUNN2</expression>
         </transformation>
         </transformations>
         </attribute>
         </attributes>
         </item>
         
         

         Canonical:

         <item>
         <type>CanonicalPartyRelationshipSales</type>
         <attributes>
         <attribute>
         <name>relationshipTypeCP</name>
         <model>
         <localizable>false</localizable>
         <collection>false</collection>
         <type>String</type>
         <primaryKey>false</primaryKey>
         </model>
         </attribute>
         <attribute>
         <name>businessCustomerNumber</name>
         <model>
         <localizable>false</localizable>
         <collection>false</collection>
         <type>String</type>
         <primaryKey>false</primaryKey>
         </model>
         </attribute>
         </attributes>
         </item>

         Target:

         <item>
         <type>CanonicalPartyReB2BUnit</type>
         <exportCode>B2BUnit</exportCode>
         <description>Update payerId</description>
         <canonicalItemSource>CanonicalPartyRelationshipSales</canonicalItemSource>
         <updatable>true</updatable>
         <filterExpression>'RE'.equals(relationshipTypeCP)</filterExpression>
         <attributes>
         <attribute>
         <name>uid</name>
         <transformationExpression>resolve('CanonicalParty').externalPartyId.concat('_').concat(salesKey)</transformationExpression>
         <exportCode>uid[unique=true]</exportCode>
         <mandatoryInHeader>true</mandatoryInHeader>
         </attribute>
         <attribute>
         <name>payerId</name>
         <transformationExpression>businessCustomerNumber</transformationExpression>
         <exportCode>payerId</exportCode>
         </attribute>
         </attributes>
         </item>

         Observed Issue:

         • The filterExpression ('RE'.equals(relationshipTypeCP)) works as expected in UAT, and the payerId attribute appears. However, in Production, the payerId is not being displayed despite having the same jar configuration.

[mansurarisoy]

Could you compare the IDoc payloads? You should see the received IDoc content with the log starting with "Received POST request /idoc/receiver/ with args" by logger com.hybris.datahub.sapidocintegration.spring.HttpInboundService

[mukulsahu7046]

Thanks for your suggestion but I'm sending the same IDOC in UAT and production but still getting this issue any other idea you want to suggest. 

[mansurarisoy]

Are you sending IDoc via Postman? Can you try to investigate loading orders of the extensions? It might be some extension which overrides your definition or prevents your extension to be loaded. I suggest you to investigate startup logs for both environments.

[mukulsahu7046]

Thanks for your suggestion. There is the same branch deployed for DEV, UAT, and Production, and I am sending the same IDoc for all environments. However, while it works perfectly fine in lower environments like DEV and UAT, it encounters issues in Production. If, as you suggest, the issue is related to loading extensions, could you help clarify why it still works fine in DEV and UAT but fails in Production? Additionally, if you suspect that extension overriding might be the cause, could you suggest how and where to check the logs for extensions to verify this? Looking forward to your guidance.

[mansurarisoy]

If everything, including the configuration (manifest.json and Data Hub configuration), is the same, then it should work as you stated. The only issue that I can think of is the extension loading order. For example, in UAT, extension-A might be loaded before extension-B, but in PROD, extension-B might be loaded before extension-A. This could cause problems if your logic depends on overriding some definitions from an existing extension. So, I suggest you investigate your custom extensions and their dependencies.

Another issue could be a problem in extension loading, which you can see in the logs during startup. Search for the name of your extension and see if there are any logs stating that the extension is unable to load.

Additionally, I suggest you check the item attributes via the API (SAP Documentation for Using the REST API to Gather Transactional Information). You should disable cleanup to prevent the items from being cleaned so that you can investigate how the items are created.