File to RFC Scenario

[phanikumar_akella]

Dear Experts,

I am working on a File to RFC scenario. I need to create an equipment, if it is already existing I need to update it. ABAP team has already developed two BAPIs (for EP screens) one for creating and other for updating. Can I reuse these BAPIs in PI Interface development?

I mean how can I use these two RFCs for creating and updating in single Interface development. Do I need to go for RFC lookups?

Or do you advice me to go for a new BAPI development with both Create/Update functionality embedded in it.

Need help...Thanks in Advance.

[former_member200962 · Accepted solution]

I am working on a File to RFC scenario. I need to create an equipment, if it is already existing I 
need to update it.

there should be some field in the File which will tell you whether it is an update or insert....suppose there is field by name ID and if it appears then it is an update...if not then it is an insert...as it is being performed for the first time....

ABAP team has already developed two BAPIs (for EP screens) one for creating and other for 
updating. Can I reuse these BAPIs in PI Interface development?

If the update and insert functionality performed by thee BAPIs is the same as you need then yes you can use it.....

Regards,

Abhishek.

[phanikumar_akella]

Thanks, Closing this thread.

[Former Member]

Hi PhaniKumar,

I'd suggest you to use either your own rfc lookup or ask you developers to create additional querying bapi to find out equipment existence. In any way you can use bpm to query the target system and then make a decision - update or create new equipment.

Regards,

Dmitriy.