Skip to main content

SAP MM - Master data

There are two types of data in SAP :

1. Master data

2. Transaction data

Master data: It is a kind of data that doesn't change regularly i.e., static in nature

For example: if you require a bank account, we are required to fill some kind of application form where our personal details are given like name, email address, etc... this is called master data

Transactional data: Master data is the basis for transactional data. Transactional data changes regularly.

For example: based on the application bank account number is generated by the bank which will be used for performing transactions.

Master Data :

There are different types of master data in MM :

1. Vendor Master data

2. Material master data

3. Purchase info records

4. Source list

5. Quota arrangement

6. Service Master data...

There are other master data as well like Output, conditions, etc which are used during transactional data processing

Master data is created through an easy access screen and is non-transportable. It is required to maintain each system across the landscape individually.

Businesses own the master data in the company and there will be site data managers who manage them.

In case of interfaces :

Partner profile maintenance comes under master data and needs to be maintained in each system





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.
Post a Comment
Read more

[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
Post a Comment
Read more

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...
1 comment
Read more