The material description is presented on the Purchase Requisition's language and not on the user language in the SAP transaction MIGO

Here I am explaining the reason behind the different language usage of the material description in case of purchase requisitions and its subsequent postings, like the goods receipt posting in MIGO.

According to the standard system design it can happen that the material description is not displayed on the user's language but on the language of the purchase requisition.      

Explanation                

When we create a Purchase Requisition (ME51N), the document is created in the logon logon language (field EBAN-SPRAS).                                       
The language is not displayed in the document. We can only see it on the database.                                                  
 

Example:                                                                         
In ME51N:                                                             
->if we are logged on 'FR' we will see the material short text in 'FR' 
->if we are logged on 'EN' we will see the material short text in 'EN' 
                                                                         
But once the Purchase Requisition has been created, in ME53N:                                   
-> if we are logged on 'FR' or 'EN' we will only see the material short text depending on what we have in EBAN-SPRAS field.

This means that if it was created in 'EN', even if now we are logged on 'FR' we will see in 'EN'.                     
                                                                         
The program will select the following fields:
EBAN-MANDT                                                               
EBAN-BANFN                                                               
EBAN-BNFPO                                                               
EBAN-TXTZ01                                                              
EBAN-SPRAS                                                               
                                                                         
So if we created in 'EN' we will only see the material short text in 'EN' in ME53N. If we created in 'FR' we will only see the material short text in 'FR' in ME53N.

As a consequence, the document creation language will be considered in subsequent postings like the Purchase Order (ME23N) and the Goods Receipt (MIGO), even that logon language is different.  

Difference between Vendor Consignment and Customer Consignment

 The main differences between Vendor Consignment and Customer Consignment in SAP:

Consignment type	Definition	Special Stock	Stock table	How to assign material to consignment stock?	How to consume material from consignment stock?
Vendor Consignment	Vendor is the owner from the consignment stock and it is stored in your company	K	MKOL	Via Purchase Order (101 K).	201 K, 261K - via cost center, order
Customer Consignment	Your company is the owner from the consignment stock, and it is stored at the customer’s company.	W	MSKU	Via SD process (631).	633 W - via shipping (SD process).

Price differences (PRD) If the PO Net price has the same value than standard price in SAP

Price differences (PRD) when the PO Net price has the same value than standard price in SAP

This page is to explain how it is possible to have price differences when the Purchase Order Net Price has the same value that standard price in the material master data.

Here is an example to justify the standard system design.

Standard Behavior

Because the rounding rule adopted by SAP system is restricted to two decimal places. It affects the goods receipt valuation calculation.

SAP note 107206 explains this behavior in details.

Example

This example show us price differences when the values are the same:

Data:       

PO qty: 99 KG          

PO Net price: 10,04 EUR  

PO Price Unit: 100 KG

A)     Create a Purchase Order in ME21N.

ME21N – Create Purchase Order

B)      Post a partial Goods Receipt for the Purchase Order in MIGO

Data:               

GR qty: 87 KG

MIGO – GR for PO

C)      Calculate the GR value (WRX)

Data:  

PO qty: 99 KG  

PO Net price: 10,04 EUR  

PO Price Unit: 100 KG    

GR qty: 87 KG

Formulas:  

PO Net Value = Po qty x (Po Net price / Po Price Unit)   

GR value (WRX) = GR qty x (PO Net Value / PO qty) 

Calculation:        

PO Net Value = Po qty x (Po Net price / Po Price Unit)  

 PO Net value = 99 KG x (10,04 EUR / 100 KG)        

PO Net value = 9,9396 EUR             

PO Net value = 9,94 EUR

GR value (WRX) = GR qty x (PO Net Value / PO qty)     

GR value (WRX) = 87 KG qty x (9,94 EUR / 99 KG)    

GR value (WRX) = 8,7351 EUR   

GR value (WRX) = 8,74 EUR  

D)     Calculate the stock account value

Data:              

Standard Price: 10,04 EUR   

Price unit: 100

Formula:     

BSX = GR qty x (Standard Price / Price Unit)   

BSX = 87 KG x (10,04 EUR / 100 KG)       

BSX = 8,7348 EUR                

BSX = 8,73 EUR                                       

MM03 – Display Material – Accounting 1

E)      Calculate the price difference value

PRD = BSX – WRX           

PRD = 8,73 EUR – 8,74 EUR  

PRD = 0,01 EUR

F)      Check FI document via ME23N (PO history), MB03 (via material document) or in FB03 directly. See that stock account was debited on 8,73 EUR, clearing account was credited on 8,74 EUR and, as a consequence, price difference account was debited on 0,01 EUR.

ME23N – Display Purchase Order


 
 

Source:https://help.sap.com/docs/SUPPORT_CONTENT/erpscm/3362168409.html

How to post a stock transfer for Consignment Material

1) Transferring Consignment Material within a plant from one storage location to another.

Example: Same plant – different storage locations

We should use movement type '311 K' in MIGO transactions. 

2) Transferring Consignment Material within a plant from one stock type to another

Example: Same plant --from blocked stock to quality inspection stock

We should use movement type '349 K' in MIGO transactions.

3) Transferring Consignment Material Into Own Stock 

Example: Same plant --from consignment tock in unrestricted-use to own stock in unrestricted-use

We should use movement type '411 K' in MB1B or MIGO transactions.

Tips:

If the material was entered in the blocked stock:

Ø  We should first transfer the material to the unrestricted-use stock K (MIGO transaction - movement type 343 K).

Ø  Once the material is in the unrestricted-use stock K, we can post the transfer to own with the movement 411 K.

Ø  The same process applies to transfer the Sales Order Stock (411 E) or the Project Stock (411 Q).

It is not possible to make the transfer directly from the blocked stock.

4) Is it possible to transfer consignment material from one plant to another (plan-to-plant scenario)?

Please see the attached note 13006.                                            
                                                                               
As indicated in the note, it is not possible to transfer vendor consignment stock from one plant to another. This functionality is not supported in any version of SAP R/3/ECC.             
                                                                               
The workaround outlined in the note is as follows:                             
 "We can post the stock transfer in two steps:                                
 1.  Post the stock issue in the issuing plant using movement type 562 in combination with the special stock indicator 'K', for example.        
                                                                               
 2.  Post the stock receipt in the receiving plant using movement type 561 in combination with the special stock indicator 'K', for example."                                                                
                                                                                
A stock transfer by means of a delivery is also not supported (movement types 641, 643, 647). This process is only supported when Retail is active.                               
Please see the IMG documentation for movement type '641', as follows:          

"641 Goods issue for a stock transport order (Shipping)                      
                                                                               
The quantity is transferred using a delivery in Shipping from unrestricted-use stock of the issuing plant to stock in transit of the receiving plant . 

                                                           
The goods receipt for the stock transport order takes place using movement type 101 and can, if required, refer to the purchase order or to the delivery. If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movement type 671. 

                          
Possible special stock indicators:                                            
E, Q, K (Retail)                                                             
For the special stock indicators E, K, and Q, and for purchase orders with account assignment, we must ensure that the quantity is not posted to the stock in transit of the receiving plant.

We can use the special stock indicator K only if you have activated the business function Retail (EA-RET)." 

How to select 'OK' for all line items in MIGO

 This page is to explains how to select/deselect all line item 'OK' buttons in transaction MIGO.

Overview

When posting a Goods Receipt in transaction MIGO, we may need to know how to select all/deselect 'OK' buttons for all line items.

 

Having multiple line items to be received, we would like to have an option in MIGO screen to select/deselect all line items together.

 

Example:

Go to transaction MIGO.

Select option 'Goods Receipt' for 'Purchase Order'.

Insert a Purchase Order number which contains several line items to be received.

Execute.

Notice that SAP System brings all line items with 'OK' button empty. In case, we would need to mark each 'OK' button manually.

 Root Cause

This is the standard system design for transaction MIGO.

 Options to Overcome this issue

Option 1: Default Values 

We can go thourgh MIGO, clicking on menu Settings > Default Values.

Here, we can activate "Propose the Ok Function in Future".

This way, 'Item OK' will be defaulted in MIGO every time, end-user does not have to mark/activate it during MIGO processing. 

Option 2: Transaction SHD0

We can go through transaction SHD0 and proceed by entering MIGO Transaction Code.

Here, activate 'Item OK' indicator and make it display so end-user will not be able to change it in MIGO.

Option 3: BAdis

We can use BAdi MB_MIGO_BADI - enhancement MBCF0005 to manipulate MIGO subscreens.

Delivery Completed Indicator is automatically removed in SAP MBRL transaction

 Delivery Completed Indicator is automatically removed when navigating through the MBRL transaction

This page is explaining the reason because the delivery completed indicator is automatically removed under certain circumstances.

Example: > PO Item was created with underdelivery = 10,00%

> PO qty (ordered qty): 269 GAL                                                

> GR qty (received qty): 264 GAL                                               

264 GAL is more than 98% of 269 GAL.  

In this case, the reason for removing the delivery completed indicator automatically in MBRL would be because we are defining underdelivery for 10,00% but the difference from the received quantity is less than 2% of the ordered qty.                                                

                                                                                

Note 81853 says that:    

"...If the items are adopted, a check is made whether a goods receipt quantity smaller than/equal to the underdelivery tolerance quantity results from this issue posting. If so, the system automatically cancels the "Delivery completed" indicator..."                                          

........................................................................       

Please also see the solution segment from this note:                           

........................................................................       

"...In order to draw our attention to the fact that the "Delivery completed" indicator is cancelled, the system now generates message 'M7 244' if it is set.                                                            

We can enter the "Delivery completed" indicator again if this message is generated.                                                                  

The indicator is then no longer changed automatically by the system..."        

........................................................................       

The big point here is to keep message 'M7 244' as 'warning'.                 

According to the standard system design the delivery completed indicator will be cleared. We have to set 'M7 244' as 'warning' to alert you and then put the delivery completed indicator manually in MBRL. 

APIs on SAP Business Accelerator Hub

 

APIs on SAP 

Ø  An application programming interface (API) is an interface that lets software systems communicate with each other and exchange data.

Ø  By offering an API for your system, we can define which data should be exposed and thereby maintain control. As the consumer of an API, we don’t have to know how the other system works. Instead, we can focus on how it's integrated into your system.

Ø  we can use the APIs available for SAP S/4HANA Cloud for these scenarios:

• Connect business processes across your system landscape
• Integrate with external systems
• Develop your own dependent extensions or custom applications

Inbound and Outbound Services

Ø  APIs can either be inbound or outbound services.

With respect to SAP S/4HANA Cloud as the source system,

Ø  Inbound means that SAP S/4HANA Cloud provides a service that another system can consume.

Ø  Outbound means that SAP S/4HANA Cloud consumes a service that is provided by another system.

 Synchronous and Asynchronous Services

APIs can either be synchronous or asynchronous services.

Ø  Synchronous means that when a system sends a request it waits for the receiving system to send a response. This approach is useful if an immediate and real-time response is required. However, both systems need to be online the entire time and if there’s an error, the request has to be sent again.

Ø  Asynchronous means that when a system sends a request it waits for the receiving system to acknowledge receipt of the message. However, it doesn’t wait for the receiving system to send a response. This way you can loosely couple systems and there’s less dependency on the availability of the other system. Additionally, the sender system isn’t blocked after sending a request and can send further requests. With this approach, you get no immediate response, and a response message needs to be implemented and routed separately.

Communication Scenarios

To establish secure communication between systems, you first need to create a communication arrangement. Communication arrangements are based on a communication scenario. Predefined communication scenarios are available for different use cases, for example, the integration of employee data. In a communication scenario, you can define a set of inbound and outbound services for a business process. Each API on SAP Business Accelerator Hub is associated with at least one communication scenario. With the communication scenario, you get an idea of the best practices for using the API. For more information, see Communication Management.

Service Categories

APIs created by SAP are categorized according to the main purpose of the messages being communicated. These service categories exist:

Application-to-Application (A2A)

A2A services facilitate the exchange of business information between different systems to connect business processes within company borders.

 Application-to-Cross Application (A2X)

A2X services facilitate the exchange of business information between a system and an unspecified client. They’re often used to build user interfaces (UIs) based on the back end, without an intervening communication layer. For this reason, A2X messages contain all the necessary information for understanding the message, such as the code names or texts to be displayed on the UI.

Business-to-Business (B2B)

B2B services facilitate the exchange of business documents across companies.

Source:https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/1e60f14bdc224c2c975c8fa8bcfd7f3f.html