BOD Connector

ANZCSV - BankStatement Loading

ANZCSV - BankStatement Loading is done for Load.BankStatement_Inbound.

Program/Business class/Process affected:

1. Files changed:
   • SM_ION_LoadBankStatement_Inbound.lpd
2. New required setup:
   • Added new System Configuration Parameter "LoadBankStatement_In_CashManagementGroup”. Default value for the flag is " ".Give the CashManagementGroup.
3. New Variable Added in JSON: No
4. New IPA Changes:
   • Added Conditions in node BankAccount
   • Added new nodes BankStatement,Branch7360, Assign1960,BankStatementLine, Assign470, Assign2260, Assign3300, Assign3490, IONAlert2140.
5. Integration Specific: No

Use these steps to test the enhancement:

1. Setup: Enable the receiver for FSM_ION_LoadBankStatement_Inbound.lpd. Pass the CashManagementGroup in system configuration parameter "LoadBankStatement_In_CashManagementGroup"
2. How to test: When the BOD gets processed, BankStatement and BankStatementLines get created.
3. Verify the result: BankStatement and BankStatementLines should get created without errors.

JT-1503505

Sync.Invoice_Inbound BOD - Native LPL Conversion

Developed Sync Invoice Inbound BOD in Native LPL.

Program/Business class/Process affected:

1. Files changed:
   • FSMARInboundBODImport.busclass
   • FSMARInboundBODImport_NativeCompany.java
   • UserTemplate
   • FSMInboundBODTracker.busclass
2. New required setup:
   • Set System value in System configuration parameters "SyncInvoice_Inbound_System".
   • Set System value in System configuration parameters "SyncInvoice_Inbound_BatchNumber".

To test the enhancement:

1. Setup: Enable Sync.Invoice_Inbound BOD in FSMBODConfiguration.
2. How to test: Send valid XML and record should create in ReceivableInvoiceImport business class.
3. Verify the result: Check record in ReceivableInvoiceImport.

JT-1424323

Need Date Adjustment - EAM Maintenance Order Interface Updates FSM PO

>> What was the issue or shortcoming?

FSM_ION_SyncMaintenanceOrder_Inbound: Need Date adjustment (PurchaseOrderLine.EarlyDeliveryDate updated) when EAM Maintenance Order Interface updates FSM PO.

Program/Business class/Process affected:

1. Files changed:
   • FSM_ION_SyncMaintenanceOrder_Inbound
   • PfiConfigurationProperty.xml
   • IEFINPostUpgradeAction BusinessClass

3.New Variable Added in JSON: No

4.New IPA Changes:

a. In Start node added the following variables:

- Added new System Configuration Parameter "UpdateRequestedDeliveryDateTimeFromWO" and assigned it to "UpdateRequestedDeliveryDateTimeFlag" variable

- UpdateScheduledStartDate,listID,UpdateRequestedDeliveryDateTime,POLineCompany,PurchaseOrderID,idx4,DocReferencelength,splitPurchaseOrder,PONumber,textName4,textValue4,textValue5,PurchaseOrderLineNum

b. Added JavaScript code in "Assign3550" for checking if the ScheduledStartDate is existing value or updated value.

c. Added switch case logic in "Assign3420" for "UpdatePOLine" query.

d. Added JavaScript code in "Assign3280" to retrieve PurchaseOrder , PurchaseOrderLine and Company values from XPaths: MaintenanceOrderLine/DocumentReference = "PurchaseOrder"/DocumentID/ID and PurchaseOrderLine from Xpath :MaintenanceOrderLine/DocumentReference/LineNumber.

5.Integration Specific: Yes

These changes are related to CSF-EAM Integration.

JT-1488510

Clean DOC ID Solution - SyncAccountingEntity Outbound

Clean DOC ID Solution - SyncAccountingEntity Outbound.

Note: This parameter is Only applicable for Beta customer and not existing customer using GFC & HRCM Integration.

Program/Business class/Process affected:

1.Files Changed:

->FSM_ION_SyncAccountingEntity_Outbound.lpd

2.New Required Setup:

->Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.

->Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.

3.New Variable Added in JSON:No

4.New IPA Changes:

->In Start node added new variables ConfigDocID,ConfigFEG,CrossAE,AChartXML.

->Added Conditions in node GLAE_VAR.

->Updated the XML Node XML_GLAE.

5.Integration Specific:No

Use these steps to test the enhancement:

1. Setup:

->Enable the service "AccountingEntityService" for FSM_ION_SyncAccountingEntity_Outbound.lpd

->Pass the source AccountingEntity and destination AccountingEntity values in Cross Reference :CSFAEVSDESTAE

2. How to Test:

->Create,Update and delete an AccountingEntity.

->BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncAccountingEntity_Outbound.lpd BOD.

3. Verify the Result:

->If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.

->If RequiredCleanDocumentID=Y then DocID and Accountingentity is CrossReference destination value.

JT-1507072

Clean DOC ID Solution - SyncAccountingEntity Outbound

Program/Business class/Process affected:

1.Files Changed:

->FSM_ION_SyncAccountingEntity_Outbound.lpd

2.New Required Setup:

->Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.

->Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.

3.New Variable Added in JSON:No

4.New IPA Changes:

->In Start node added new variables ConfigDocID,ConfigFEG,CrossAE,AChartXML.

->Added Conditions in node GLAE_VAR.

->Updated the XML Node XML_GLAE.

5.Integration Specific:No

Use these steps to test the enhancement:

1. Setup:

->Enable the service "AccountingEntityService" for FSM_ION_SyncAccountingEntity_Outbound.lpd

->Pass the source AccountingEntity and destination AccountingEntity values in Cross Reference :CSFAEVSDESTAE

2. How to Test:

->Create,Update and delete an AccountingEntity.

->BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncAccountingEntity_Outbound.lpd BOD.

3. Verify the Result:

->If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.

->If RequiredCleanDocumentID=Y then DocID and Accountingentity is CrossReference destination value.

JT-1507072

Clean DOC ID Solution - Sync.AccountingChart Outbound

Clean DOC ID Solution - Sync.AccountingChart Outbound.

Note: This parameter/change is Only applicable for Beta customer and not existing customer using GFC & HRCM integrations.

Program/Business class/Process affected:

FSM_ION_SyncAccountingChart_Out.lpd

>> What should I test?

File Changed:

1.FSM_ION_SyncAccountingChart_Out.lpd

2.New Required Setup: No

3.New Variable Added in JSON: No

4.New IPA Changes:

In FSM_ION_SyncAccountingChart_Out IPA flow below changes done:

a.In Start node : Added ConfigDocID,ConfigFEG,CrossAE,TriggerCrossReference and AEntity variables.

b.Branch2830: Added Branch.

If ConfigDocID ="Y" it will go to CleanDocumentID chnages flow, else Standard flow.

c.Added AE Transaction node, Assign6670,Branch630,XML6560 and IONOutbox9250

5.Integration Specific: Yes

These changes are specific to GFC & HRCM Integration.

1. Setup:

1.In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

2.Enable the Service Definition and Processes for FSM_ION_SyncAccountingChart_Out IPA flow.

Go to Service Definition and Enable "ReportingChartService" for "FSM_ION_SyncAccountingChart_Out.lpd" Processes.

3.Do the setup in CrossReference.

4.In System Configuration CleandDocID= "Y" and TriggerBODBasedOnCrossReference ="Y" and (IsMultipleFEG = "N" or IsMultipleFEG = "Y")

If IsMultipleFEG = "N"

In Cross Reference CSFAE value should pass as AE

If IsMultipleFEG = "Y"

In Cross Reference CSFAE value should pass as FEG@@AE (FEG concatenation with AE)

1.Create/Update ReportingChart.

2.BOD will trigger and Work unit will generate successfully with required CleanDocumentID changes.

JT-1507073

Clean DOC ID Solution - Sync.ChartOfAccount Outbound

Clean DOC ID Solution - Sync.ChartOfAccount Outbound.

Note: This parameter is Only applicable for Beta customer and not existing customer using CSF-GFC & CSF-HRCM Integration

Program/Business class/Process affected:

FSM_ION_SyncChartOfAccounts_Out.lpd

Use these steps to test the enhancement:

File Changed:

1.FSM_ION_SyncChartOfAccounts_Out.lpd

2.New Required Setup: No

3.New Variable Added in JSON: No

4.New IPA Changes:

In FSM_ION_SyncChartOfAccounts_Out IPA flow below changes done:

a.In Start node : Added ConfigDocID,ConfigFEG,CrossAE,TriggerCrossReference and AEntity variables.

b.Branch7990: Added Branch.

If ConfigDocID ="Y" it will go to CleanDocumentID chnages flow, else Standard flow.

c.Added AE Transaction node, Assign8600,Branch1860,XML9920 and IONOutbox4690

5.Integration Specific: Yes

These changes are specific to GFC & HRCM Integration.

1. Setup:

1.In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

2.Enable the Service Definition and Processes for FSM_ION_SyncChartOfAccounts_Out IPA flow.

Go to Service Definition and Enable "ReportingChartAccountService" for "FSM_ION_SyncChartOfAccounts_Out.lpd" Processes.

3.Do the setup in CrossReference.

4.In System Configuration CleandDocID= "Y" and TriggerBODBasedOnCrossReference ="Y" and (IsMultipleFEG = "N" or IsMultipleFEG = "Y")

If IsMultipleFEG = "N"

In Cross Reference CSFAE value should pass as AE

If IsMultipleFEG = "Y"

In Cross Reference CSFAE value should pass as FEG@@AE (FEG concatenation with AE)

Execution:

1.Create/Update ChartAccount.

2.BOD will trigger and Work unit will generate successfully with required CleanDocumentID changes.

JT-1507079

Local.ly : Trigger Sync.Shipment_Outbound BOD from OE/BL (Sales transport Document), New trigger point to be added once we release the shipment.

Added a trigger code in Sync.Shipment_BOD for Local.ly

Program/Business class/Process affected:

1.Files Changed: WarehouseShipment.busclass

2.New Required Setup: No new setup is required.

3.New Variable Added in JSON: No new variable is added in JSON

4.New IPA Changes: invoked the trigger code in FinalRelease action in WarehouseShipment.busclass

5.Integration Specific: Changes are related to Local.ly integration.

Use these steps to test the enhancement:

1. Setup:

-In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

-For Outbound BOD, Enable the Service Definition "ShipmentService" and Process "FSM_ION_SyncShipment_Out"

2. How to Test:

-Create and Release CustomerOrder

-Run WarehousePickListPrint batch job

-Navigate to WarehouseShipment and perform Finish>>Release action

3. Verify the Result:

-BOD gets triggered and Work Unit is generated successfully

JT-1510523

Expense Report BOD - Consuming Dimensions of CSF as Segments

Consuming Dimensions of CSF as Segments based on Classfication type = "CostCenterSegments' in FSM_ION_SyncExpenseReport_In BOD

Program/Business class/Process affected:

1.Files Changed:

FSM_ION_SyncExpenseReport_Inbound

2.New Required Setup:No

3.New IPA Changes:

- In Start node, added variables "CostCenterClassificationType","CostCenterClassificationlen","idx4","textName4","textValue4"

- In "Assign7160" and "Assign3680" nodes added JavaScript code for getting Cost Center value:

if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is "CostCenterSegments", reading the value from ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/Codes/Code listID = "Cost Center"

if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is not available then reading the value from ExpenseReport/ExpenseReportLine/ExpenseAllocation/CostCenterCode

5.Integration Specific: Yes

These changes are related to CSF-XM Integration.

Use these steps to test the enhancement:

1. Setup:

- In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

- In Channels Administrator, Activate the respective ION Inbox Receivers for FSM_ION_SyncExpenseReport_Inbound.

2. How to Test:

- When the ExpenseReport is processed form XM side, "ExpenseManagementStagingHeader" and "ExpenseManagementStagingDetail" are created and is moved to "ExpenseManagementInterfaceHeader" with line records in "ExpenseManagementInterfaceDetail".

- BOD will trigger and Work unit will be generated successfully without any error for FSM_ION_SyncExpenseReport_Inbound BOD.

3. Verify the result:

if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is "CostCenterSegments", reading the value from ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/Codes/Code listID = "Cost Center"

if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is not available then reading the value from ExpenseReport/ExpenseReportLine/ExpenseAllocation/CostCenterCode

JT-1512175

SyncSupplierInvoice_Out - BOD Changes for Ditributions

Sending Distributions type "Distribution" data is now available for Local.ly.

JT-1518786

ION Content and JSON Files Delivery -CU77

The latest IPA JSON files and FSM_ION_CONTENT* delivery -

JSONFILES_ST record is updated in \iefin\wfdata\SampleDocumentTemplate.

The FSM_ION_CONTENT* record is updated in \iefin\plugins\iefinconnector\ipa_content.

JT-1531257