Skip to main content

List of configurations to be done for creation of a Plant

MM Configuration for the plant :

Creation of the plant - V_T001W
Assignment of storage location to the plant - V_T001L
Assignment of the valuation area to Company code - V_T001K
Assignment of the purchase organisation to the plant - V_T024W
Maintain stock and value update for the respective material types linked to the plant - T134M
Maintain Plant parameters - V_159L
Maintain negative stocks to the storage location ( if required ) - MM ---> IM ---> Goods issues

SD Configuration for the plant :

Shipping point determination - TVSTZ
Assign sales organization - distribution channel - plant - V_TVKWZ_ASSIGN
Assign shipping point to plant - V_OVXC
Define, copy, delete, check shipping point - V_TVST
Storage location determination - V_TVKOL

PS configuration for the plant :

Specify Parameters for Network Type - V_T399X_NN
Specify Parameters for Network Scheduling -  V_TCX00_FAUF
Define Checking Control -  V_TCO11
Define Confirmation Parameters - V_TCORU_P

In case of Plant belongs to India :

Business area need to be created as a part of FI settings - V_TGSB

Comments

Post a Comment

Popular posts from this blog

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...