Is there any way to transfer the Start date of Pur Requisition from APO (RRP3 screen) to ECC ME23N?

[ritam_nandy]

Hello Experts,

There is a requirement to reflect the Start date of a Purchase Requisition/PO in the RRP3 view of APO system to the corresponding PO in ME23N transaction as a text field in the ECC system. Could you please let me know if you have got any idea about having any such instances? Would be obliged if you could help me with such enhancement idea or the User Exits used there.

Thank you.

-Ritam

[RahulHanda · Accepted solution]

Hi Ritam,

Logically you already have this. If you go to Purchase requisition (ME53n) on quantities/dates tab, you see release date which logically should be equal to start date in APO. If not let me know if you are scheduling margin key on MRP2 tab.

As far as PO is concerned you always see the requested delivery date or confirmed delivery date in APO as start date. Are you directly creating POs in APO system, this is what you are saying. Coz result is always planned orders. PRs, STOs and you convert them.

So basically what I can imagine of is that you want to copy start date of PR to PO while converting in some field, is it the case?

Regards

Rahul

[ritam_nandy · Accepted solution]

Hi Rahul,

Thanks for your reply. In your case, yes, the Release date of the PReq in ECC matches with the Start date of the corresponding PReq in the APO side, provided the Planned Delivery Time matches in both the systems.

But now, for the scenario where we are using the TLB Order to directly to convert into the STO, we are not having this PReq stage in the ECC side - hence no such help here. Any idea on this scenario, where we are trying to convert the TLB Order to STO directly from the APO?

Thanks.

-Ritam

[ritam_nandy]

Got it - the Function Module /SAPAPO/OM_ORDER_GET_DATA gets the Start date of the Order in APO.

Meanwhile, just found some scenarios where the Release date of the PReq in ECC system doesn't match with the Start date of the corresponding Order in the RRP3 view in APO system - any idea what could be the reason?

[tejbonagiri]

Hi Ritam,

Can you please suggest on how you handled this. In our case there are two MoTs (Air & Boat) in APO and default is Boat (as per PIR in ECC). Even though, a PReq coming from APO has Air, Release date in ECC is based on Boat (based on default in PIR). So, we want to control this in ECC based on MoT from APO,

[Former Member]

As you probably already know, the APO start date is NOT CIF'd to ECC as there is no corresponding field in ECC.   You mentioned you had a text field in ECC to "hold" this value.

So of course you can have a user exit ready the APO Pur Req start date and transfer it to ECC into this text field.  But how will this help?  You should still represent in ECC which MOT (air/ship/ground) APO selected in the ECC pur req.   Also what will happen if the buyer changes the shipping instructions in ECC (changing ground to air for example)?

Ken

[tejbonagiri]

Hi Ken,

Thanks for responding.

So, the expectation is users change MoT in APO only. Now, we want to influence Release Date in APO based on MoT selected in APO. As you have pointed, this is possible through exit in ECC. The plan is to change PDT in PReq in ECC based on MoT in APO which will automatically change the Release Date of PReq in ECC.

This Release Date is important to be right (based on MoT in APO) as PReq to PO conversion happens based on it. Once PReq is converted to a PO, they can change the Shipping Instructions in PO and it is more of execution decision and APO just respects PO's Delivery Date.

Somehow, ECC is over writing the PDT we have put (based in MoT in APO) with PDT maintained in PIR. So, just curious, if there is a setting to prevent ECC from auto calculating the Release date, but at the same time have PIR information as it is needed during conversion to a PO.

Best Regards,

Tej

[Former Member]

Can you specify what you are actually trying to accomplish.   Are you referring to dates for pur req's or PO's?   The opening date is CIF's to the ECC Release Date and is normally not changed.  

Now STO's there are options to prevent rescheduling by the other system.

[tejbonagiri]

Hi Ken,

We want to change Release Date in a PReq based on MoT selected in APO. We are able to do this finally by changing the PDT in PReq based on MoT selected in APO (overwriting the proposed PDT by ECC based on PIR). We are good now. Thanks for the support.

Best Regards,

Tej

[Former Member]

Are you saying the pur req opening date in APO was not CIF'ing to the ECC release date?

The opening date in APO already considers the MOT that APO selected.  ECC will not change this date.   For PO's this is a different issue.  But for Pur Req's no custom code is required.  I am curious why it was not working for you.

[tejbonagiri]

We noticed that, for a PReq Opening Date calculated by APO is being changed in ECC based on PIR information (which has Default PDT).

So calculation of Release date is happening in ECC based on PDT maintained in PIR. We had to put an exit to overwrite this calculation.

Please suggest if there is a standard way to do this,

Best Regards,

Tej

[Former Member]

that is interesting.

APO opening date is calculated using GR Time, GI Time, Transp Lane Duration, and Opening Period so obviously won't match the Pur Info Record planned delivery time.

So you are saying if you have a Transp Duration of 30 days and the pur info rec has a planned delivery time of only 2 days.  the ECC Pur Req Release date will use the pur info rec planned delivery time of 2 days and so will be totally different from the APO opening date?

I have not seen that. 

We are NOT talking the ECC request date.  You are talking about ECC Release Date EBAN-FRGDT.

Ken

[tejbonagiri]

Yeah Ken, I'm talking about ECC Release Date.

But, one thing we noticed is that APO Opening Date calculation is based on GR/GI/Lead Time in PIR. It is irrespective of Transportation Duration (Tlane is created based  on PIR and hence PIR lead time stored in header data)

Eg: GR Time = 5 Days, MoT-Air = 1 Day, MoT-Boat = 30 Days, PIR Lead Time = 61 Days, GI Time = 0 Days.

If we create 2 PReqs one with Air & other with Boat with End Date as 12/14/2016, Opening Date will be 10/09/2016 for both the PReqs (12/14/2016 - 5 - 61). Same is the case with Release Date in ECC.

So, we have put this logic in ECC to change Release Date in ECC based on MoT selected.

After this customization,

Release Date in ECC for MoT Air is 10/09/2016 (12/14/2016 - 5 - 61)

Release Date in ECC for MoT Boat is 09/09/2016 (12/14/2016 - 5 - 90)

Best Regards,

Tej

[Former Member]

I think you are mistaken.

THe Opening date is CIF'd to ECC release date and is not changed.

Opening Date = APO End Date - APO GR Time (Receiving Calendar) - Max(Transportation Lane  Duration, APO Planned Delivery Time) - APO GI Time (Shipping Calendar) - APO Opening Period (Shipping Calendar)   

So your planned delivery time is too large.   Why have a transportation duration so small.

In fact you should set the planned delivery time to zero in APO if you have a transportation lane into that location.

Ken

[ritam_nandy]

Hi All,

Is there any way to debug the Outbound Queue from APO system? - may be then, we can try to find the appropriate Exit for this. When we are blocking and trying to 'debug LUW', the queue gets triggered and moves out.

Thanks.

[RahulHanda]

Hi Ritam,

First stop the outbound queues with /SAPAPO/CIFSTOPQUEUES and then you can do the same.

Regards

Rahul

[Former Member]

Hi Ritam,

On ECC side you have:

Thanks, Marius

Change and Enhance Purchase Order Data

Use

You can use enhancement CIFPUR02 to change purchase order data that was transferred by SAP APO before a purchase order or purchase requisition is created in the ERP system.

For more information, see the documentation for enhancement CIFPUR02.

Activities

1. Create the enhancement.

For this, either create a new project or use an existing project.

2. Activate the project.

• Your enhancement only becomes effective when you activate the project.

On APO side:

Influence Publication of Purchase Order Documents

Use

You can use enhancement APOCFPEP to change external procurement documents, for example, purchase orders and purchase requisitions, in a customer-specific way before they are published to SAP R/3.

Activities

1. Create the enhancement.

To do this, either create a new project or use an existing project.

2. Activate the project.

1. You have to activate the project in order for your enhancement to take effect.