WDF 2540038 – Copy GRPO to AP Invoice enhancement in document exchange cycle

WDF 2540038 – Copy GRPO to AP Invoice enhancement in document exchange cycle

The Intercompany cycle has been enhanced to offer greater flexibility by allowing the Goods Receipt PO (GRPO) to be copied directly to the A/P Invoice or the A/P Invoice to be copied directly from the Goods Receipt PO (GRPO) in the receiving company under specific conditions. This is particularly useful when items in the Purchase Order are substituted with alternate items in the Sales Order generated from the sender company's Purchase Order.

In certain scenarios, when a GRPO is created based on a delivery, the customer may change the items in the GRPO before adding the document. As a result, the final GRPO may contain different items than those listed in the original delivery document from the sender.

Subsequently, when the sender's delivery document is copied to an A/R Invoice and added, a draft A/P Invoice is automatically created in the receiving company, reflecting the items from the A/R Invoice.

At this stage, the items in the draft A/P Invoice are often manually modified to match those in the GRPO before the document is added. However, since the items in the base GRPO were changed, the added A/P Invoice loses its base document linkage, resulting in inventory being deducted twice.

To prevent this issue of double inventory deduction,  a new option has been added to the Intercompany General Settings: "Allow 'Copy To/Copy From' between Goods Receipt PO and A/P Invoice."


Note:

  1. This setting is configured per company. When enabled, all users within the company can copy Intercompany GRPO documents directly to A/P Invoice documents.
  2. When adding the A/P Invoice, the system will prompt the user with a confirmation message to close any open Purchase Orders (POs) associated with the A/P Invoice.
  3. Upon adding the A/P Invoice, the system will also check if a draft Intercompany A/P Invoice already exists for the same transaction. If found, it will prompt the user for confirmation before closing the draft.

Manual Handling Scenarios:

The following scenarios must be handled manually when a GRPO is copied to an A/P Invoice:

  1. A/P Credit Memo Based on A/P Invoice:
    • If an A/P Credit Memo is created based on an A/P Invoice that originated using a "Copy To/Copy From" based on the GRPO, the corresponding A/R Credit Memo will replicate as a stand-alone document in the sender company.
    • The user must manually reconcile this A/R Credit Memo with the respective A/R Invoice.

 

  1. Goods Return Based on GRPO:
    • If a Goods Return is created based on a GRPO that was generated via "Copy To/Copy From," the return will replicate as a stand-alone document in the sender company.
    • The user must manually close the replicated Goods Return.

 

  1. A/R Invoice Created After A/P Invoice:
    • If an A/R Invoice is created in the sender company after the A/P Invoice has already been added in the receiver company, a draft A/P Invoice may still exist in the receiver company.
    • The user must manually close the draft A/P Invoice.
Workaround:
Step - 1
The attached zip files (count 2) are to be imported via BizStore Import of Control Center.

1. From your existing environment, take the backup of "com.cxs.b1i.repository" and "com.sap.b1i.dev.scenarios.design" file as per the backup process below:

To take a backup of the repository files, perform the following steps:
  1. Log in to Integration Framework 2.0.
  2. Go to Tools -->Control Center --> Maintenance -->BizStore Export.
  3. In the Exporting Content from BizStore, in the selection criteria. Select the Dataset button.
  4. In the Choose Dataset, Choose Value "com.cxs.b1i.repository" and then press the Submit button.
  5. Save the file in the relevant folder.
To take a backup of the package file, perform the following steps:
  1. Log in to Integration Framework 2.0.
  2. Go to Tools -->Control Center --> Maintenance -->BizStore Export.
  3. In the Exporting Content from BizStore, in the selection criteria. Select the Dataset button.
  4. In the Choose Dataset, Choose Value "com.sap.b1i.dev.scenarios.design", Choose Group "CXS.IC", and then press the Submit button.
  5. Save the file in the relevant folder.
2. Perform the following steps to import the Repository file:
  1. Log in to Integration Framework 2.0.
  2. Go to Control Center --> Maintenance -->BizStore Import.
  3. In the Importing Content to BizStore, in the selection criteria. In the Choose Archive, select the Choose File button. 
  4. Select the repository file "com.cxs.b1i.repository.temp2.zip".
  5. Select the checkbox Assume File System-Friendly Naming and then Submit.
3. Perform the following steps to import the Package file:
  1. Log in to Integration Framework 2.0.
  2. Go to Control Center --> Maintenance -->BizStore Import.
  3. In the Importing Content to BizStore, in the selection criteria. In the Choose Archive, select the Choose File button. 
  4. Select the package file "com.sap.b1i.dev.scenarios.design.zip".
  5. Select the checkbox Assume File System-Friendly Naming and then Submit.
4. Log in to Intercompany Administration Console, navigate to the Landscape, and redeploy the IC solution.

Step -2:

i. Download the Intercompany (ICO) Version 54 Hotfix Add-On version 54.3 from here.

ii. Apply the hotfix add-on to all companies across the landscape.


Solution:

The enhancement described above will be incorporated in the Intercompany Integration Solutions version 55 and higher versions.

Product
Product or Product Version
B1 INTERCOMPANY INTEGRATION
SAP B1 10.0 FOR SAP HANA
SAP B1 9.3 FOR SAP HANA
SAP BUSINESS ONE 10.0
SAP BUSINESS ONE 9.3

This document refers to : 
WDF 2550001 - Overview Note for Intercompany integration solution Version 55 for SAP Business One