Skip to Content
0

SFDC integration and LOT of look up to see if record exists in SFDC, good practice?

Feb 07 at 08:16 AM

16

avatar image
Former Member

Dear Experts

We are on SAP PO 7.4 and we have lot of integration scenarios with SalesForce or Glovia especially order to cash interfaces.

Problem: We have lot of look up in place at SAP PO side to SFDC(SalesForce) via SalesForce adpater within SAP PO mapping layer.

Why:

1. To determine if order(corresponding to delivery number received from SAP) exists or not at SFDC side, some time to fetch SFDC parent id of object, sometime even worse PO should determine (by lookup to SFDC)if it is INSERT or UPDATE or DELETE operation at SFDC side and

2. then call appropriate receiver SFDC adpater to perform required CRUD operation(Create, Read, Update, Delete).

In my opinion, this is not so optimized design where we pass SalesForce complexity to Middelware layer and it could worse performance of SAP PO and other interfaces.

Questions:

  • Do you suggest some SAP standard guideline where we should limit look up or when should we use look ups(in my opinion for data enrichment only)?
  • Do you have similar issues , where PO has to do look up while sending data to SFDC to determine operation(insert,...) or fetch relevant SFDC parent id?
  • If you can pass SAP guideline regarding this, also welcomed.

Br

Divyesh

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers