Skip to main content

Customer Account Group Creation

Customer Account Group acts like a backbone for customer master data and is pre-requisite for creation of customer master data.

Ideally Individual account groups will be created based on the below parameters.
  • Field Status
  • Number Ranges
  • Partner Functions
  • Type of Customer I.e., Regular or One Time Customer
For domestic customer GSTIN number is mandatory whereas for export customers it is not.

further, We can  create individual account groups for 'One time account', 'Ship to Party', 'Bill to Party' and 'Payer'.

So due to that individual account groups need to be created in this case for both export and domestic customers,  'One time account', 'Ship to Party', 'Bill to Party' and 'Payer'.


Field Status Control

Path:

Goto SPRO - Financial Accounting New - Accounts receivable and Accounts Payable - Master data - Define Account Group with Screen Layout ( Customers) ( T.Code - OBD2)



Create new account group with reference to existing one or use the existing account group.



Maintain the required data in the newly created account group. If this account group is meant for one time customer then select the check box - One time account.

Else if this is meant for regular customers then leave it blank.




Select the below field status data to control fields .



Suppress - This is used to hide a field

Req. Entry -  This is used to make a field manadatory

Opt. Entry -  This is used to make a field Optional.

Display - This will disable the field for data entry

As a best practice it is better is suppress the fields which are not required by the business user.

Comments

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...