How to control PGI process between Sales and Supply Chain in SAP S/4HANA Public Cloud?

[Ayanuddin]

Hi Experts,

We are working with SAP S/4HANA Public Cloud (web-based Fiori apps, though standard TCodes like MMBE are still available).

Here’s the scenario:

1. Using MMBE, suppose we have 10,000 stock available.

2. Multiple salesmen are creating sales orders, deliveries, posting PGI, and invoices.

3. Sometimes, one user leaves the process incomplete (e.g., delivery created but invoice not done).

4. After PGI, stock reduces in the system (e.g., from 10,000 → 5,000). However, when we check physical stock, it shows a mismatch (e.g., 6,000 physically available).

5. This causes stock visibility and accountability issues for the supply chain team.

Requirement:
Instead of Sales doing PGI, we want to shift PGI responsibility to the Supply Chain team. This way, stock movement is fully controlled and monitored by them, avoiding mismatches and conflicts.

My question:

• Is there a way in S/4HANA Public Cloud to restrict PGI so that only the Supply Chain team can execute it (not Sales)?

• If yes, what’s the best practice or standard way to achieve this?

Thanks in advance for your guidance.

[Dominik_Tylczynski]

Are you saying that PGI of 5,000 reduces stock from 10,000 to 5,000 but MMBE still shows 6,000?

[_MansurHerfy]

The ability to perform PGI (Post Goods Issue) in SAP Fiori hinges entirely on the authorization profile, specifically the Business Role and Business Catalog assignments.

So yes, if Sales users lack the catalog that includes the PGI functionality, they won’t be able to execute PGI—even if they can create deliveries. That’s by design: SAP’s role-based access ensures users only perform actions aligned with their responsibilities.

• Who should have access to PGI?

Typically, PGI is granted to roles such as:

• Warehouse Clerks or Shipping Specialists – who physically handle goods and confirm dispatch.

• Logistics Execution Users – responsible for outbound processes.

• Delivery Processing Roles – if PGI is part of their workflow.

These users would be assigned a Business Role that includes the Business Catalog containing the PGI app (e.g., "Outbound Delivery Processing" catalog). You can fine-tune access further using restriction values like shipping point, plant, or delivery type to ensure users only act on relevant data.

If you’re setting this up, make sure:

• The correct Fiori app (e.g., Post Goods Issue for Outbound Delivery) is included in the catalog.

• The catalog is assigned to the right Business Role.

• The role is assigned to the appropriate Business User.

[_MansurHerfy]

To enable Post Goods Issue (PGI) functionality in SAP Fiori, you'll need to assign the correct Fiori app and Business Catalog to the relevant Business Role. Here's the precise info you need: 📦 SAP Fiori App for PGI App Name: Post Goods Issue for Outbound Delivery App ID: F1595 Semantic Object: OutboundDelivery Action: PostGoodsIssue This app allows users to post goods issue for outbound deliveries directly from the Fiori Launchpad. 📚 Business Catalog To enable this app, assign the following catalog: Catalog ID: SAP_SD_BC_OUTBOUND_DEL_PROC_MC Catalog Name: Outbound Delivery Processing This catalog includes the PGI app along with other outbound delivery-related apps like Change Outbound Delivery, Display Outbound Delivery, and Create Outbound Delivery. 👤 Who Should Get It? Assign this catalog to roles such as: Shipping Clerk Warehouse Operator Logistics Execution Specialist Sales users typically should not have this catalog unless they are directly involved in logistics execution. This ensures proper segregation of duties and avoids unauthorized PGI actions.