Custom Checks for Block Overrule Checkbox

 With the block refactoring done in TM 9.4 we introduced the functionality to overrule specific blocks by the user to still enable process steps like planning, execution or invoicing.

The functionality was well received but we often get questions from customer projects about a more granular control over which kind of blocks should be overrulable e.g. “Compliance blocks should never be overruled” or which user should actually be able to overrule blocks.

We did not provide any customizing our authority object to handle this, but with wise foresight  we already built the functionality in a way that it can easily be enhanced in your project to perform additional checks when clicking the “Overrule Blocks” checkbox.

The initial part of this enhancement is of course generic and well known to most of you, but I include it to provide an end-to-end guide:

Creation of Enhancement BO for /SCMTMS/TOR

Open Transaction BOBX.

On Header Toolbar Select Business Object Processing Framework -> Create -> Business Object Enhancement

Enter the name of your new enhancement business object according to the naming conventions of your project. For Super Business Object enter /SCMTMS/TOR.

Navigate to your enhancement object. The Object contains the structure of its original Super BO /SCMTMS/TOR.

Creation of Action Validation for Action Block~Overrule_Block

In the node tree of your Enhancement Object. Navigate to Node BLOCK -> Validations. Right click on folder validations and select Create Validation -> Action Validation.

Open Tab Trigger Actions. And select Action Block~OVERRULE_BLOCK

Maintain action as below.

 

 

 

 

 

After creation the implementing class is still empty.

Open Transaction SE24 and create a new class.

In the interface section of the class builder add interface /BOBF/IF_FRW_VALIDATION. Save the changes.

Navigate to tab methods and double click on Method /BOBF/IF_FRW_VALIDATION~EXECUTE to implement your specific logic.

In the simple example screenshot below, we will get the data of the processed block instances and check if any of the blocks(consider although on the UI you click one by one, technically the action can be called for multiple blocks at once) is of a specific kind. In this case a manual block with Block Reason Code “(29)Restriction for Follow-up processing“(Remember…just a technical example). If this is the case, we add the key of the block instance to the table et_failed_key so it will not be passed to the standard overrule processing logic later. We also throw an error message to the user saying that “Block must not be overruled”.

Activate all methods of the newly create class.

Enter the newly created class as Implementing Class in your created Action Validation of your Enhancement BO.

Result

When trying to overrule a block that matches the condition in coding snippet line 18, the overrule information(flag, user, date&time) will not be set and the User is informed by the error message returned in line 21ff above.

In regards to the 2nd example of only enabling a specific user to overrule blocks, you could of course also implement a custom authority check in your action validation.

 Source: https://blogs.sap.com/2021/09/14/custom-checks-for-block-overrule-checkbox/

 

Como evitar o erro do TXJCD na tabela J_1BNFDOC?

Publicado por:Renan Correa06 de setembro de 2021

Compartilhe:

Quem já precisou fazer uma “correção manual emergencial” na tabela J_1BNFDOC  já deve ter se deparado com o erro abaixo (  algumas pessoas chamariam pelo nome científico de “marretada” ;D )

Entrada  SP 3550308  não existe na tabela TTXJ (check entry)

Sabe porque isso ocorre?

Isso acontece por causa da definição do campo na J_1BNFDOC… Ele usa o campo TXJCD com a tabela de verificação TTXJ:

Essa é a definição do campo:

O problema é que a tabela TTXJ não é a tabela de domicílios usada no BR. Então, mesmo que você tenha o docmílio cadastrado para Brasil vai acontecer esse erro.

Para evitar o erro é necessário criar uma entrada na TTXJ com o domicílio preenchido e o campo do esquema de cálculo em branco ( sim, a J_1BNFDOC não tem o esquema de cálculo então o acesso que ele faz na TTXJ é apenas com MANDT e TXJCD ).

Depois de criar a entrada na tabela TTXJ o sistema deixa salvar a “correção manual emergencial” na tabela J_1BNFDOC.

Uma curiosidade, existe um campo específico da localização Brasil para domicilios fiscais. O campo usado da localização é J_1BTXJCD e a tabela de verificação é a J_1BTXJUR ( onde estão todos os dominílios ), mas não é usado na J_1BNFDOC.

Moral da história: Por favor não alterem as tabelas, mas se precisar por algum motivode força maior então façam do jeito certo. Eu acho que o campo J_1BTXJCD podia estar na doc no lugar do TXJCD, mas isso é achismo meu.

Se vocês conhecem outro jeito de corrigir isso, fala aí nos comentários. 

Valeu Gurizada,

Renan

Source: https://s4cn.com/como-evitar-o-erro-do-txjcd-na-tabela-j_1bnfdoc/

SAP® Extended Warehouse Management 2020 Development Overview, Part 2 – Enhanced Integration

 In our previous blog of the 4-part series covering the enhancements brought to SAP EWM by the SAP S/4HANA 2020 release we presented a detailed overview of the improvements we made in the area of User Experience. With this blog, I want to go over what is probably the biggest part of our release: the enhanced Integration. While the main focus was on various production related improvements and innovations, we also enhanced the integration to Quality Management, Serial Number handling and more.

Synchronous Goods Movements from Manufacturing to EWM

Now with synchronous goods movement from Manufacturing to EWM, all updates will be synchronized between the warehouse management and inventory management systems. Through this improvement, users can experience better stock synchronization, avoid monitoring of asynchronous processes and queues, reduce documentation (no inbound and outbound deliveries) and mix consumption from MM-IM and EWM storage locations in one posting.

It is important to note that while this feature was available in the 1909 release, it was only for repetitive manufacturing. Now with S/4HANA 2020 SAP EWM supports the following processes:

• Confirmations (GR / GI) using discrete and process manufacturing (for repetitive available since 1909)
  • Transactions CO11N, CO15, COR6N, CORK and others
  • Synchronous backflush using PMR (for cross order- and single order parts)
  • Batch determination in EWM for component backflush (REM & PP)
  • Co- and by-products
  • Automatic putaway WT creation
  • Re-processing with COGI
• Confirmations with HUs (transaction MFHU)
• Goods receipts for HUs from production (transaction COWBHUWE)
• GR and GI for order / reservation with transaction MIGO
• Document-neutral and document-specific reversals
• Kanban for in-house production strategies ‘working with production orders’
• PP confirmation BAPIs and APIs
• MM-IM BAPI_GOODSMVT_CREATE and BAPI_GOODSMVT_CANCEL

We have also included several options to control automatic creation of putaway tasks, as shown in the picture below.

Additionally, we integrated the UI between MM-IM material document display in MIGO and EWM. For that we added a new tab ‘Warehouse Management’ in MIGO on item level to support synchronous posting for:

• GR and GI for order
• GI for reservation
• Cancel and return delivery for material document
• GR for summarized JIT call

This new tab offers visibility of receiving / consumption bin, EWM material document and EWM putaway task. Furthermore, you can directly navigate from this tab to the EWM warehouse monitor to show material document or putaway tasks.

We are only scratching the surface with this blog, but you can find more details in the “SAP Extended Warehouse Management – scope of 2020 release” document linked here and at the end of this article. One final important point to mention is that this feature is available only for the embedded SAP Extended Warehouse Management on SAP S/4HANA version.

Stock Transfer Kanban Improvements

We also made three improvements in the area of Kanban, available only for the embedded SAP EWM version. Firstly, we made it very intuitive to reverse the Kanban status from FULL to EMPTY in case of user error. EWM warehouse tasks as well as the goods movement shall be reversed. The reverse from FULL to EMPTY process will automatically post stock back into EWM storage locations, put stock back into source storage bin, and re-create warehouse tasks to replenish Kanban. With this enhancement users will save time and reduce errors that can occur during the manual reversal process.

A second improvement for Kanban is the new default exception code we added for setting Kanban FULL with a difference in quantity. Before the 2020 release, it was not possible to enter differences in the “Set KANBAN Container Status” Fiori App but an error message was raised. Now when entering differences for stock transfer with EWM warehouse task, a default exception code is set in the background. This exception code can be customized in the warehouse process type.

Lastly for Kanban, we have added the Inventory Management material document and GM document to the Kanban information display. By double clicking on the document numbers you can navigate forward to each option. This will make navigation and troubleshooting more intuitive.

Enhancements to Quality Management

There are also three enhancements we made in the area of Quality Management. The first and biggest is the integration to QM defects and notification. With this new solution we want to capture defects for products in EWM managed warehouses or production supply areas (PSA), do stock assignments and follow-up actions triggering stock postings for one or multiple materials, all in EWM. Stock that needs inspection can be posted to “Blocked” or “Quality stock”, and after investigation warehouse workers post the stock to ‘free available stock’, ‘scrap to cost center’, ‘return delivery’ or ‘move stock’. Please note that this solution is available only for EWM embedded version.

Another improvement in QM integration is the addition of two new follow-up actions when specifying accounting objects in quality usage decisions. Now users can specify if an object is ‘Scrapped to cost center’ or is posted to ‘Sample consumption’. The example below illustrates how posting an object to scrap would look like in the system. Currently this enhancement is for the embedded EWM version, but we plan to make it available for Decentral SAP EWM on S/4HANA with the Feature Pack 1 release of 2020.

One final enhancement to mention in the area of QM integration is the integration of QM in the production part approval process for first article inspections. First article inspections are controlled in the quality info record by maintaining the corresponding purchase order item for first article delivery. This makes communication between manufacturers and suppliers easier and more efficient.

Enhancements to Serial Number Management

For Serial Numbers we have added a new customizing option that enables harmonized serialization on client and plant level. Harmonized Serial Number Profile includes ERP as well as EWM serialization. The harmonized serial number profile brings ERP and EWM settings together in one profile thereby making it possible to validate the profile in advance before using it. Users will notice that a lot of redundancy will be avoided thanks to this harmonization, as well as the ability to decide on entitled level whether a product should be serialized or not.

Aside from harmonization users can also repair serial number profiles via a new monitor method to delete serialization settings stored in the EWM warehouse product and maintain new profiles. This serial number repair is only possible when no open warehouse tasks, open delivery items or warehouse stock exists.

Accounting Information in Ad-Hoc Goods Movements

A minor but no less significant improvement is the enhancement of the transaction /SCWM/ADGI Post Unplanned Goods Issue. Now with transaction /SCWM/ADGI users can post goods movement for the consumption, scrapping and sampling processes. The account assignment can be changed for a single item when a partial goods issue is posted. For warehouse documents posted with transaction /SCWM/ADGI the account assignment can be displayed in the warehouse monitor.

JIT Supply to Production – Stock Transfer for JIT Call

Finally, I would like to present what is arguably the biggest integration topic of this release, Just-in-Time (JIT) supply to production. The integration with this new solution covers the internal replenishment process for JIT in production supply for the automotive industry. Warehouse workers can now transfer stock from EWM managed storage locations to EWM managed production supply areas (PSA) to accurately and timely supply the production line. The lightweight warehouse request ‘internal stock transfer’ acts as an interface between JIT and warehouse order processing. Please note that this solution is provided for the embedded EWM version only.

The JIT supply to production process in EWM includes the following functions:

• Creation of stock transfer for JIT followed by an immediate automatic warehouse task creation in EWM, a manual warehouse task creation in EWM or a warehouse task creation via wave management in EWM
• Change management from the JIT call to the stock transfer for JIT call
• Process and quantity updates from EWM to JIT during warehouse order processing
• Monitoring with the EWM warehouse management monitor
• An enhancement concept with new BAdIs

Just as with the synchronous goods movement enhancements, there are a lot more details to cover for this topic, so I again highly encourage you to check the “SAP Extended Warehouse Management – scope of 2020 release” .

FIND OUT MORE!

There are more minor integration topics that may be worth your attention, such as the global transport label support (GTL) for handling unit management, and you can read about them and the topics we covered above in our “SAP Extended Warehouse Management – Scope of the 2020 Release” document in the following link:
https://dam.sap.com/mac/embed/public/pdf/v/mzWrXsc.htm

In case you missed the first part in our overview series, you can find it in the link below:
https://blogs.sap.com/2020/10/08/sap-extended-warehouse-management-2020-development-overview-part-1-improved-user-experience/

For more information about SAP Extended Warehouse Management, please follow us on social media, our YouTube channel or our community pages:

SAP EWM Community:

https://www.sap.com/community/topics/extended-warehouse-management.html

SAP Digital Supply Chain Channel:

https://www.youtube.com/channel/UCELmE2CEAkcwqpBLnuZHufA

EWM LinkedIn Community:

https://www.linkedin.com/groups/1952257/

Release information and restrictions of embedded EWM on SAP S/4HANA 2020:
https://launchpad.support.sap.com/#/notes/2938306

Release information and restrictions of Decentralized EWM on SAP S/4HANA 2020:

https://launchpad.support.sap.com/#/notes/2938308

For a complete list of Q&A from the EWM community, please access this link:
https://answers.sap.com/tags/01200615320800000705

In case you do not find your specific question there, feel free to post your question via the following form:
https://answers.sap.com/questions/ask.html?primaryTagId=01200615320800000705

Source: https://blogs.sap.com/2020/10/14/sap-extended-warehouse-management-2020-development-overview-part-2-enhanced-integration/?utm_campaign=meetedgar&utm_medium=social&utm_source=meetedgar.com

EWM – Vendor Returns Process – Returns Delivery Vs Returns PO

 SAP offers 2 different processes of Vendor Returns: returns with Returns Delivery Ref to Inbound Delivery and returns with Returns PO. So what is the difference? In this blogs I will compare this 2 processes with EWM steps.

My Testing is based on Embedded EWM – S/4HANA 1909.

 

Compare Vendor Return Process with Returns Delivery Ref to Inbound and Returns PO

• Overall Process with EWM steps

• Comparation

 

Prerequisite

• Active BC Set – /SCWM/DLV_OUTBOUND_RETURN

Configuration

General Customizing

• Set up confirmation Control Key

IMG: MM > Purchasing > Confirmations > Set Up Confirmation Control

Assign 0004 as Quantity Difference Profile

IMG: MM > Purchasing > Confirmations > Set Up Quantity Difference Profiles (GR Automotive)

IMG: MM > Purchasing > Confirmations > Define Internal Confirmation Categories

• Shipping point determination

IMG: Logistics Execution > Shipping > Basic Shipping Functions > Shipping Point and Goods Receiving Point Determination > Assign Shipping Points

• Define shipping data (For Returns PO)

IMG: Material Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Define Shipping Data for Plants

Need to create a BP as Customer for Plants and assign BP here.

• Check “Delivery Split” in delivery Type

IMG: Logistics Execution > Shipping > Deliveries > Define Delivery Types

• Delivery Item Type Determination

IMG: Logistics Execution > Shipping > Deliveries > Define Item Category Determination in Deliveries

EWM Customizing

• Mapping Delivery Type and Item Type S/4HANA & EWM

• Determine WPT for Return Doc Type

• Define Storage search sequence

Note: Assign GR Interims Storage Type 9010 to search sequence of Return Delivery

• Determine Storage Type search sequence

 

Master data

When using Returns PO, Vendor master data and Material Master data need some additional data as below.

• Vendor Master data:

For using Return Delivery, in Role Vendor, mark Vendor as Return Supplier.

For using Returns PO, maintain Customer roles for Sales.org & Distribution Channel. Assign Delivery Plant as plant where you returns stock.

• Material Master data:

For using Returns PO, maintain Sales View for material.

 

Testing

Vendor Returns – Using Returns Delivery Ref to Inbound Delivery

Step 1: Create Return Delivery Ref to Inbound

Tcode: /SCWM/PRDI

Before this step, a Inbound Delivery is created and GR is posted.

Stock is still in GR-ZONE, mean if you already putaway stock and confirmed putaway WT, you need manually transfer stock to GR Zone.

Step 2: Create Picking WT and Confirm WT

Tcode: /SCWM/PRDO

Note: Stock is taken from GR-ZONE to GI-ZONE

Step 3: Post GI 

Tcode: /SCWM/PRDO

Post GI after picking is completed.

Note: Stock Type is Q3 (or F1)

Material Document with Mvt 122 is created in S/4HANA

 

Vendor Returns – Using Returns PO

Step 1: Create Retuns PO

Tcode: ME21N

Select PO type – PO Return and mark Item as Return Item

 

Step 2: Create Outbound Delivery

Tcode: VL10B

Step 3: Create Picking WT and Confirm WT

Tcode: /SCWM/PRDO

Step 4: Post GI 

Tcode: /SCWM/PRDO

Post GI after picking is complete.

Note: Stock type is Q4 (or F2)

Material document is created with Mvt 161

— End —

 

In which case will you use Returns Delivery Ref to Inbound or Returns PO? Feel free to question/comment on my Topics.

 

Regards,

Van Dang

 

Reference

Returns PO

https://help.sap.com/doc/cd4e70ed816d46aba0661d1cd5c1eabb/3.6/en-US/de6a3d45bb814393b04cff7fd6b9aefd.html

Returns Delivery

https://help.sap.com/viewer/91b21005dded4984bcccf4a69ae1300c/2020.000/en-US/e263bd534f22b44ce10000000a174cb4.html

 Source: https://blogs.sap.com/2021/09/10/ewm-vendor-returns-process-returns-delivery-vs-returns-po/