What is the preferred/fully functional method to UPDATE Business Partners in a SAP S/4HANA for Retail 1709 implementation?

Answered

DSP User

• April 09, 2018 12:06

We are working in a SAP S/4HANA for Retail 1709 implementation. What is the preferred/fully functional method to UPDATE Business Partners in a similar setup?

RFC_CVI_EI_INBOUND_MAIN doesn’t do the trick. RDS Data Services job seems to call the same function. Is there a new/preferred method to update BP, Customers and Suppliers tables in case we need to perform updates? Many thanks in advance.

1

• Best answer

  

  DSP Expert

  • April 09, 2018 13:10

  PCardoso: More on this. The below note draws a firm line in the sand with 1709 FPS02 that RFC_CVI_EI_INBOUND_MAIN is no longer supported. The exact wording is: "The API RFC CVI_EI_INBOUND_MAIN will not be supported from the release SAP S/4HANA On Premise 1709 FPS2 and in Cloud Edition 1805 onwards." 

  https://launchpad.support.sap.com/#/notes/2405714 

  My sense of urgency on a resolution to this is heightened now. Upon investigation, I can confirm that this API is not RFC-enabled, and to use it (in Integrate, LSMW or to create a custom object using LTMOM) requires a FM wrapper to be created. I am not sure what resources (or timing pressures) you have on your side, but essentially, the requirement is to:

  1. Have an FM created and enabled for RFC call that exposes the API structure (CVIS_EI_EZTERN).
  2. Per OSS note, the FM Pass the data in CVIS_EI_EXTERN structure format and pass it to the method VALIDATE_SINGLE. This method validates all the data that is passed; after that, you can use the method MAINTAIN to create business partners.

  0
• 

  DSP Expert

  • April 09, 2018 12:32

  PCardoso:

  SAP has provided guidance that 1709 RFC_CVI_EI_INBOUND_MAIN is no longer supported.

  That guidance is firmer with the recent release of FPS02. What are you trying to update in BP that you are finding RFC_CVI_EI_INBOUND_MAIN will not work? We are doing extensive Business Partner enrichment at our client and have been successful with 1709. The new API provided is CL_MD_BP_MAINTAIN and is outlined in the OSS here: https://launchpad.support.sap.com/#/notes/2417298.

  We will be moving to this new API at our client, pending our testing against FPS02. Chatter on this change indicates that the old API will continue to work in many use cases, since SAP internally needs time to accommodate this change. RDS and Migration Cockpit content (to-date) has not addressed this change.  

  0
• 

  DSP User

  • May 02, 2018 04:25

  accepted

  0
• 

  Philip Loo

  • November 09, 2021 16:06

  In ECC,  KCLJ is used to load FSCM data which BP Credit Profile.   This same method, KCLJ External Data Transfer can also be used to update BP.   Here is the process:

  • Create Sender Structure – KCLL
  • Create Sender Structure Table – Dictionary structure with data fields for transfer
    • Due to access permission, requires solution team to create new sender structure
    • SE80 Object Navigator -> Development Object – To view
    • AKTYP – Edit Mode
      • 01 – Add Mode
      • 02 – Update Mode
    • Assign Sender Structure Table to Sender Structure in KCLL
    • KC7R Transfer Rule to map Sender Field to BP table BUT000 data field
    • RJB1 External Data Transfer Work Bench
    • Create Export package to export data file for use in KCLJ
    • Execute KCLJ
    • Transport to other SAP Client for execution.

  

  0

Please sign in to leave a comment.