GI not triggered for PSA

[former_member573898]

Hi EWM experts,

I am configuring the production integration with EWM.

The scenario is 1 EWM Sloc as a source and the destination production Sloc is only IM managed.

I have successfully configured for outbound delivery creation.

After WT creation and confirmation, the stock is at the PSA but it is not automatically GI.

I have made settings for automatic GI in the below areas

1. SCM Extended Warehouse Management --> Extended Warehouse Management --> Goods Issue Process --> Outbound Delivery --> Production Supply --> Maintain Settings for Aut. Goods Issue for Production Supply

2. /SCWM/PSA - Define PSA

So, I don't know why GI is not triggered

[former_member573898 · Accepted solution]

The problem is solved.

[former_member543347]

Hi Tri,

I never used this particular trigger, but it is a PPF actions. Debug a PPF action is not different than debugging any other piece of code, only you need to activate system & update debugging.

1. Set a breakpoint in the piece of code you want ot debug.
2. Start the debugger with /h.
3. Settings > Change debugging profile/settings. Activate sytem debugging & update debugging and save.
4. Now pick something for production replenishment, to trigger the PPF action.
5. The debugger will pop up when the PPF action starts (thus moving to the foreground an action that usually runs in the background). At this point you should re-load all breakpoints (not sure if it is needed, but I think so). Let the code run and it will stop in the breakpoint you set in step 1.

[former_member573898]

Hi Julio,

Thanks for your response.

From the view of a functional consultant, I don't know where to set a breakpoint... before I confirm the WT or even before that.

But I think the ABAP consultant might know this.

[former_member543347]

Hi Tri,

I don't think you need the checkbox "Post GI" in this case, but I'm not sure.

I understand your concern about performance, and personally I also avoid background jobs as I find triggers more elegant and low-maintenance, but it of course depends on the business scenario. If you have many picking WTs and you are triggering a partial GI every few seconds, your system will be more overloaded than if you just post everything every 30 minutes. The question is how fast you need the GI. According to SAP (pay attention at the last sentence), triggering GI at stock arrival in the PSA can be a performance killer.

Trigger Goods Issue (GI) at PSA

Indicates whether you want to post the goods issue (GI) for a production supply delivery when the stock arrives at the production supply area (PSA).

Use

You can set this flag if a regular job for posting the GI using program Post Goods Issue in PSA is not sufficient, and if you want to have the stock available in the ERP storage location earlier.

Dependencies

• The system only evaluates the field if you use the outbound delivery process for production supply deliveries.

• If you want to post the goods issue from the PSA, you have to register the document type for the automatic GI in the IMG activity Maintain Settings for Aut. Goods Issue for Production Supply.

• Depending on the number of delivery items in the PSA, setting this flag increases the system load. SAP recommends that you only set it for a PSA in which you are expecting a small data volume.

[former_member573898]

Hi Julio,

Thanks for your comment. I'll adjust my approach when it comes to this :).

The workaround might be come the direct solution :).

Just for scientific exploration, in my Q system, I use the check instead of the regular job. Now it is not working due to timezone problem. How can I debug this?

[former_member543347]

Why don't you simply create a periodic background job with SM36?

• Maintain a variant with your desired parameters for report /SCWM/R_DLV_POST_GI_PSA (or T-Code /SCWM/DLV_GIPSA).
• SM36, create a job with one step: program /SCWM/DLV_GIPSA, the variant you just created.
• Enter the desired start time (or select "Immediate") and the desired period.

[former_member573898]

Hi Julio,

It can be a workaround. If I do this, do I have to maintain the checkbox "Post GI" in the PSA?

The reason why I say it is a workaround is because background jobs slow the system down. This is the testing system, so we have only 3-4 plants. But in a production system, there will be roughly 30-40 plants/warehouses. Each will have different requirement about time so we will have 30-40 jobs just to post GI, which is quite unnecessary from my perspective when SAP has given you a standard solution. We just need to find out why it is not working :((((

My intention is ask for support from an ABAPer, but I don't know how to explain the situation to him with enough details to work...

[petrzak]

Hi,

can you check if you maintained the system time zone correctly? Table TTZCU, value tzonesys.

Background jobs are always created in the system time zone by default.

Regards,
Petr

[former_member573898]

Hi Zak,

The system timezone is CET. My user's timezone is UTC+7 which is before CET.

From my understanding, if the system uses my user ID to set up the job, it should pick my user ID's timezone...

[former_member573898]

Hi all,

I would like to change my question.

The job is created using my user ID. But the time in the background job is not user timezone of my user ID.

So why is the user timezone not be picked for job creation?

[shailesh_mishra5]

Hello,

Please check the Warehouse and consumption posting delivery has below settings.

If you materials are marked with backflush, then automatic consumption in IM 261 simultaneously triggers Consumption delivery CP.

The action profile that is assigned to the delivery type(PDO) must contain action /SCWM/PRD_OUT_POST_GI_PP .

Check the required Action profile which is responsible for consumption posting in EWM.

The action definition /SCWM/PRD_OUT_GI_PP is responsible for Auto GI posting and it should be active.

Best regards

Shailesh Mishra

[former_member573898]

Hi Shailesh,

Thanks for your comment.

However, my issue is about PGI from EWM SLoc to IM (Production) SLoc after stock has been putaway to the PSA.

I have used SM21 like Zak suggested and found that due to the time-zone difference, the job start time was in the past and so it was not created.

The system uses my user ID to create the background job. The job start time will be scheduled based on the system time zone.

Because the system time zone is BEFORE my user ID's time zone, the job start time will always be in the past.

Now, a temporary solution might be to change my user ID's time zone to system time zone or before that. But this will not reflect the correct time in reality.

So could anyone show me how to make the system take into account the time difference between the system time zone and user ID's time zone when creating background jobs?

[petrzak]

Hello Tri,

it is possible that background job creation is failing. Please check system logs - i.e. SM21, or SLG1 for potential issues with number ranges, authorisations etc...

Petr

[former_member573898]

Hi Zak,

Thanks for your suggestion.

How can I know which job name and creator to search for?

Also, how is the background job scheduled? Is it scheduled once the putaway WT to the PSA gets confirmed?