Skip to main content

[MM] Enterprise Structure - Assignment

Enterprise Structure Assignment 

Relationship between individual org. elements are maintained here

**********************************************************

Plant to company code assignment :

Can we assign one plant to multiple company codes?

One plant can be assigned only to one company code

one company code can have multiple plants 

************************************************************

one plant can have 'N' number of storage locations

************************************************************

Purchase organization to company code assignment

Can we assign one purchase org. to multiple company codes?

One Purchase org.

Cross company code purchases

if I assign company code to purchase org. then I am restricting purchase org. to specific company code

If I do not maintain any company code in the assignment then the purchase org. can be used for purchase goods for multiple company codes

*************************************************************

Purchase organization to Plant assignment

Can we use a single purchase organization to procure stock for multiple plants ?

Many to Many relationships

**************************************************************

Standard Purchase org. assignment to plant

Reference purchase org. assignment to Standard Purchase Org.

Multiple standard Purchase org. can be assigned to the same reference. Purchase Org.

***************************************************************

Once done, Goto transaction EC02 to check if the relationship is maintained properly

****************************************************************


Comments

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).
4 comments
Read more

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more