Automate

hello
While ago now that I saw that a highly respected member of Winshuttle wrote that they are looking for creating RFM's around the terrible tcode BP.

Recordings are difficult, performance is poor and in general the SAP BAPI's can only do so much.
Furthermore you now and then run into the fact that there is the Old (ECC) "Customer" or "Supplier" number needed next to the Business Partner Number.
Hence, you'll first have to find both in order to run for example certain parts of RFC_CVI_EI_INBOUND_MAIN.

The latter is sometimes also being referred to as potentially obsolete so not really sustainable to use as a bases for future developments.
Not even speaking about the complexity of this RFC.

So, I hope there is light at the tunnel and Winshuttle is able to provide their high quality RFM...?

------------------------------
Ed Meiners | Team leader Business Applications – Master Data Integration Management
Royal Wessanen nv | +31 (0)20 3123353
------------------------------

Hi Ed,

A few comments from my perspective:

1. Your config can have the BP and customer/vendor number match, which will simplify maintenance. That is what I did in our system and makes the most sense, in my view.   I believe most customers are doing the same.  If they don't match, then I suggest a query to lookup the other associated number.  From a search I see two tables: IBPSUPPLIER, IBUPACUSTOMER.
2. Yes, there is a FM in the works, but I can't offer a timeframe nor exact contents.  The goal, in general, was to cover the most common roles for customer and vendor for create and update.  But again, I'm not 100% what will all be included in v1.
3. ​Although RFC_CVI_EI_INBOUND_MAIN is listed as not supported (and never was as far as I can tell), it has been and still is part of the Migration Cockpit, and is perfectly usable in the interim.  That's my opinion, of course.  I have posted some examples on the Community site, so that you get the general idea on how it works, since there was literally no good documentation that I could find.
4. It is also my hope that SAP will provide more OOTB BAPIs/rFMs - at least one can hope.

Hope that helps.  

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------

Original Message:
Sent: 09-16-2022 02:28
From: Ed Meiners
Subject: RFM for BP Create / Change

hello
While ago now that I saw that a highly respected member of Winshuttle wrote that they are looking for creating RFM's around the terrible tcode BP.

Recordings are difficult, performance is poor and in general the SAP BAPI's can only do so much.
Furthermore you now and then run into the fact that there is the Old (ECC) "Customer" or "Supplier" number needed next to the Business Partner Number.
Hence, you'll first have to find both in order to run for example certain parts of RFC_CVI_EI_INBOUND_MAIN.

The latter is sometimes also being referred to as potentially obsolete so not really sustainable to use as a bases for future developments.
Not even speaking about the complexity of this RFC.

So, I hope there is light at the tunnel and Winshuttle is able to provide their high quality RFM...?

------------------------------
Ed Meiners | Team leader Business Applications – Master Data Integration Management
Royal Wessanen nv | +31 (0)20 3123353
------------------------------

As always you give good answers, already these two tables i didn't know :)

Looking forward for what to come.

Thanks

------------------------------
Ed Meiners | Team leader Business Applications – Master Data Integration Management
Royal Wessanen nv | +31 (0)20 3123353
------------------------------

Original Message:
Sent: 09-23-2022 12:07
From: Sigrid Kok
Subject: RFM for BP Create / Change

Hi Ed,

A few comments from my perspective:

1. Your config can have the BP and customer/vendor number match, which will simplify maintenance. That is what I did in our system and makes the most sense, in my view.   I believe most customers are doing the same.  If they don't match, then I suggest a query to lookup the other associated number.  From a search I see two tables: IBPSUPPLIER, IBUPACUSTOMER.
2. Yes, there is a FM in the works, but I can't offer a timeframe nor exact contents.  The goal, in general, was to cover the most common roles for customer and vendor for create and update.  But again, I'm not 100% what will all be included in v1.
3. ​Although RFC_CVI_EI_INBOUND_MAIN is listed as not supported (and never was as far as I can tell), it has been and still is part of the Migration Cockpit, and is perfectly usable in the interim.  That's my opinion, of course.  I have posted some examples on the Community site, so that you get the general idea on how it works, since there was literally no good documentation that I could find.
4. It is also my hope that SAP will provide more OOTB BAPIs/rFMs - at least one can hope.

Hope that helps.  

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA

Original Message:
Sent: 09-16-2022 02:28
From: Ed Meiners
Subject: RFM for BP Create / Change

hello
While ago now that I saw that a highly respected member of Winshuttle wrote that they are looking for creating RFM's around the terrible tcode BP.

Recordings are difficult, performance is poor and in general the SAP BAPI's can only do so much.
Furthermore you now and then run into the fact that there is the Old (ECC) "Customer" or "Supplier" number needed next to the Business Partner Number.
Hence, you'll first have to find both in order to run for example certain parts of RFC_CVI_EI_INBOUND_MAIN.

The latter is sometimes also being referred to as potentially obsolete so not really sustainable to use as a bases for future developments.
Not even speaking about the complexity of this RFC.

So, I hope there is light at the tunnel and Winshuttle is able to provide their high quality RFM...?

------------------------------
Ed Meiners | Team leader Business Applications – Master Data Integration Management
Royal Wessanen nv | +31 (0)20 3123353
------------------------------