cancel
Showing results for 
Search instead for 
Did you mean: 

Integration of pegging relationship between AATP and IBP OBP

AyanBishnu
Active Contributor
0 Kudos
2,354

Hello Experts

I have a requirement where we have both IBP OBP and AATP in S4HANA in scope. what I want to acheive is the following.

1) Execute constraint forecast optimizer in OBP to generate supply plan

2) Then execute the confirmation run in IBP so that it generate the pegging relationship between each demand and supply element..

3) Now before I want to execute the deployment in OBP I want to send the reswult of the confirmation run in S4 so that AATP can repeg those exisiting pegging that cane fropm OBP and generates in own fixed or dynamic pegging in S4 AATP.

4) Then I want the AATP pegged orders to be transferred back from S4 HAN to IBP OBP where I want to run the deployment based on the revised peggng that came in from AATP

Now my question is as below

a) After the confirmation run can I transfer the orders from IBP to S4 along with the pegging that has been created as a part of the confirmatrion run ? Is that possible using the exisitng SDI outbound ?

b) Once AATP run generates the fixed / dynamic pegging in S4 can i transfer those order along with the AATP pegged relationship uysing standard SDI inbound ? Or is their a way to bring the orders back to IBP along with the AATp pegging ?

c) In case the above is possible somehow will the deployment run in IBP respecyt the pegging generated in AATP ?

Any thoughts, suggestions or prior exprience on this ? Please feel free to share.

Regards

Ayan Bishnu

Accepted Solutions (1)

Accepted Solutions (1)

AyanBishnu
Active Contributor
0 Kudos

Hi Vanam

thier are valid reasons and requirements where in we need to use both AATP and OBP confirmation in parallel. Let me explain.

  • AATP has way more features and functionalities compared to comfirmation, as we have / or will have all the rules based ATP check which far superior than OBP confirmation based on custom atribute sorting and rules created in BRF+ put together.
  • Majority of the confirmation based pegging will happen in AATP than OBP confirmation ( Aleast for org like microsoft, Apple, Adidas & Google, who rely heavily on this ATP process). Hence it a requirement to integrate pegged orders between AATP & OBP, for planning are visibility.
  • Now OBP confirmation provides JIT and stable supply methods, where the later can closely associated with fixed pegging. Moreover most org runs OBP for a 6 to 8 months horizon at daily bucket, where the first 1 or 2 months are frozen from a delployment perspective. Hence pegging relationship in those frozen period should be ideally AATP based, where in OBP it is just a view only horizon.

So in a nutshell, the requirement based on which I raised this question is as follows

  1. OBP confirmation to run and generate pegging for a 6 month horizon in IBP.
  2. The pegging then needs to be in Sync in AATP, where complex RATP process runs for the first 8 weeks and revise and repeg the orders that came in from IBP.
  3. Firmed pegging for the 1st 8 weeks goes back to IBP and confirmations run executes for the 6 month horizon without touching the pegging relationship in the frozen horizon.
rahul_kumar124
Explorer
0 Kudos

Hi Ayan,

Thanks for the explanation..

To your comment in the above post,

"I have got 50% of the solution wherein I have figured out how to transfer the pegging from IBP OBP to S4 HANA".

Can you please share the information? can it be possible in RTI(SAP7F) as well?

Thanks,

Rahul

AyanBishnu
Active Contributor
0 Kudos

Hello rahul.kumar124

As of now we are exporting the peggining from OBP to S4 using the OData feed and leveraging CPIDS and web services to integrate those pegging info to S4.

Now getting the pegging from S4 to HANA, as of now is not possible in SDI or RTI either. But down the line RTI functions will be enhanced to include pegging in integration model. But when ?? Thats the real question, for which I dont have an answer right now 🙂

Answers (3)

Answers (3)

alokdyutdas
Explorer
0 Kudos

Hello,

The transferring of pegging result from SAP IBP to S4 or ECC should be a known solution by now based on the date of the post.

I had done the solution in SDI, but the architecture should be relevant for RTI as well.

In SAP IBP, in order to transfer the pegged result you have to run the job "Data Integration: Extraction of Order-Based Planning Result". The data gets stored in 5 tables. Check this link https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/7cc6c35770994957ade465f87ac9c3d4/af0af4ce....

For these data to be transferred to S4, ECC or any ERP tool a certain set of configuration has to be done:

1. DP Agent has to be installed. Note: for integration through SDI, you can install 2 DP Agents in one server. One for Inbound eg. Abap Adaptor and another for Outbound eg. File Adapter.

2. Pegging results are always transferred through File Adapter and store the result in a .csv file. 5 files which are basically the tables mentioned in the link provided. Check Note: 2479514 - Sample .csv and .cfg files for IBP RM SDI integration

3. Now, you need to transfer those files using a shell script to S4, ECC or ERP system in custom tables. And also the shell script should delete the existing entries in those 5 files, so that for the next time it can re-populate the new pegging results in the .csv files. 

Well, now you have all the pegging results in custom table, you are good to make your own reports or customizations to carry out your business requirements. 

Note:

1. The only catch in the whole puzzle is installing 2 DP Agents in the server. This information was provided by SAP during our project, it is not documented in a simple way in sap help.

2. For RTI, I think one DP Agent should do the wonders.

 

Kind regards

Alok 

ArunIBP
Discoverer
0 Kudos

@AyanBishnu Were you able to figure out a solution to Fixed pegging? We are having a similar requirement.

lingaiahvanam
SAP Champion
SAP Champion
0 Kudos

Hi Ayan,

When you run confirmation in IBP that means orders are confirmed based on rules and priorities.

However why would you run the AATP once again in S/4HANA?

This is gray area for customers to implement confirmation run and AATP functionality together.

Best Regards,

Lingaiah