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

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

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.

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