LMV Functionality

Separation/
YDI1 Separation

for each service provider

1/27/2020 1
 LMV Functionality Separation / YDI1 Separation

• Functionality of YDI1
• Drawbacks from present capabilities of YDI1
• Benefits of separating YDI1
• Technical changes required for separation

1/27/2020 2
 LMV Functionality Separation / YDI1 Separation

• Functionality of YDI1:
 When shipment create in SAP or Change in SAP  YDI1 triggers
 Data flows from SAP to Service provider ( via Data power and F4F )
 Service providers in scope ( MACROPOINT, P44, TRANSPOREON and NUVIZZ )
 RV61B682 – YDI1 ( requirement checks to trigger YDI1 )
 Response from proxy updates to application log
 Both OK and error message
 NAST update with complete application log captured
 YDI1 fails If ( technical side )
× Service provider does not find
× Carrier code does not exist in shipment
× Smart form does not find
 YDI1 fails if ( functional side )
× Failure from requirement routine (RV61B682)
× Condition records do not maintain

1/27/2020 3
 LMV Functionality Separation / YDI1 Separation

• Determination of service provider

• Maintain application log
• Log custom data changes
• Proxy structures separation
• Using object oriented programming
• Response

1/27/2020 4