CONFIGURATIONS:

Define Company (OX15)

Explanation:

A company is the top organizational structure in SAP and can contain multiple company codes. It is
used for consolidated financial statements.

1. Enter OX15 in the command field.

2. Click New Entries.

3. Fill in the following fields:

Company: Enter a unique identifier for the company (e.g., 1000).

Company Name: Enter the name of the company.

City: Enter the location of the company.

Country: Enter the country code (e.g., US).

Currency: Enter the base currency (e.g., USD).

Language: Enter the default language (e.g., EN).

4. Click Save.

Define Company Code (OX02)

Explanation:

A company code is the smallest unit of external accounting for which a complete, self-contained set
of accounts can be created.

1. Enter OX02 in the command field.

2. Click New Entries.

3. Fill in the following fields:

Company Code: Enter a unique 4-character code (e.g., 1100).

Company Name: Enter the full name of the company code.

City: Enter the location of the company code.

Country: Enter the country code.

Currency: Enter the base currency.

Language: Enter the default language.

4. Click Save.

Link Company to Company Code (OX16)

Explanation:

Links the company to its respective company codes for consolidated reporting.

1. Enter OX16 in the command field.

2. Select Assign Company Code to Company.

3. Enter the following details:

 Company: Enter the company ID.

Company Code: Enter the company code to link.

4. Click Save.

Define Business Area (OX03)

Explanation:

Business areas are internal organizational units used for reporting across multiple company codes.

1. Enter OX03 in the command field.

2. Click New Entries.

3. Fill in the following fields:

Business Area: Enter a unique identifier (e.g., 3000).

Description: Enter the name of the business area.

4. Click Save.

Define Consolidation Business Area (OCC1)

Explanation:

Defines consolidation business areas for group-level reporting.

1. Enter OCC1 in the command field.

2. Click New Entries.

3. Fill in the following fields:

Consolidation Business Area: Enter a unique identifier.

Description: Enter the name of the consolidation business area.

4. Click Save.

Link Business Area to Consolidation Business Area (OBB6)

Explanation:

This configuration maps business areas to their consolidation counterparts.

1. Enter OBB6 in the command field.

2. Map the Business Area to the Consolidation Business Area.

3. Click Save.

Define Fiscal Year Variant (OB29)

Explanation:

A fiscal year variant determines the number and duration of fiscal periods in a year.

1. Enter OB29 in the command field.

2. Click New Entries.

3. Fill in the following fields:

Fiscal Year Variant: Enter a unique identifier (e.g., K4).

 Description: Provide a description.

Number of Periods: Enter the total number of periods (e.g., 12).

Special Periods: Enter the number of adjustment periods (e.g., 4).

4. Save.

Assign Fiscal Year Variant to Company Code (OB37)

Explanation:

Assigns the fiscal year variant to the respective company code.

1. Enter OB37 in the command field.

2. Assign the Fiscal Year Variant to the Company Code.

3. Click Save.

Posting Period Variant (OBBO)

Explanation:

Defines the rules for controlling open and closed posting periods.

1. Enter OBBO in the command field.

2. Click New Entries.

3. Define:

Posting Period Variant: Enter a unique identifier.

Description: Enter a name for the variant.

4. Save.

Assign Posting Period Variant to Company Code (OBBP)

Explanation:

Assigns the posting period variant to company codes for period control.

1. Enter OBBP in the command field.

2. Map the Posting Period Variant to the Company Code.

3. Save.

Open and Close Posting Periods (OB52)

Explanation:

Controls which posting periods are open or closed for transactions.

1. Enter OB52 in the command field.

2. Define:

Account Type: Specify the type (e.g., A for Assets).

From/To Account: Define the account range.

From/To Period: Specify open periods.

3. Save.
Define Chart of Accounts (OB13)

Explanation:

The Chart of Accounts (CoA) is a structured list of G/L accounts that define how financial transactions
are recorded.

1. Enter OB13 in the command field.

2. Click New Entries.

3. Fill in the following fields:

Chart of Accounts: Enter a unique identifier (e.g., INT for international).

Description: Provide a meaningful description.

Maintenance Language: Specify the default language.

Length of G/L Account Number: Define the character length (e.g., 10).

Group Chart of Accounts: If applicable, link to a group CoA.

4. Click Save.

Assign Chart of Accounts to Company Code (OB62)

Explanation:

This step links the defined Chart of Accounts to the company code.

1. Enter OB62 in the command field.

2. Assign:

Company Code.

Chart of Accounts.

Account Currency: Define the currency for the CoA.

3. Save.

Define Account Groups (OBD4)

Explanation:

Account groups are used to classify G/L accounts and determine field statuses during account
creation.

1. Enter OBD4 in the command field.

2. Define the following:

Chart of Accounts.

Account Group: Enter a unique identifier (e.g., 1000).

Description: Provide a meaningful description.

Field Status: Specify the field behaviour (e.g., mandatory, optional, or hidden).

3. Save.

Define Retained Earnings Account (OB53)

Explanation:
Retained earnings accounts are used for closing balances during fiscal year-end.

1. Enter OB53 in the command field.

2. Select the Chart of Accounts.

3. Enter:

Account Number: Specify the retained earnings account.

Account Type: Choose the account type (e.g., P for profit and loss).

4. Save.

Define Field Status Variant (OBC4)

Explanation:

Field Status Variants control the input behaviour of fields during document entry.

1. Enter OBC4 in the command field.

2. Click New Entries.

3. Fill in the following fields:

Field Status Variant: Enter a unique identifier.

Field Status Group: Define groups based on field relevance.

4. Save.

Assign Field Status Variant to Company Code (OBC5)

Explanation:

Assigns the field status variant to the respective company code.

1. Enter OBC5 in the command field.

2. Assign:

Company Code.

Field Status Variant.

3. Save.

Define Posting Key Rules (OB41)

Explanation:

Posting keys define how transactions are posted, such as debit or credit.

1. Enter OB41 in the command field.

2. Define:

Posting Key: Enter a unique key (e.g., 40 for debit, 50 for credit).

Account Type: Specify the type (e.g., G/L, vendor, customer).

Field Status: Control field behaviour.

3. Save.

Define Document Types (OBA7)

Explanation:

Document types classify business transactions (e.g., invoices, payments).

1. Enter OBA7 in the command field.

2. Define:

Document Type: Enter a unique identifier (e.g., KR for vendor invoices).

Number Range: Assign a range for the document type.

3. Save.

Maintain Document Number Ranges (FBN1)

Explanation:

Defines number ranges for documents created in the system.

1. Enter FBN1 in the command field.

2. Select the Company Code.

3. Define:

Number Range: Enter a unique range (e.g., 01).

From Number/To Number: Specify the range.

4. Save.

Tolerance Group for Employees (OBA4)

Explanation:

Defines limits for employees regarding cash discounts and payments.

1. Enter OBA4 in the command field.

2. Define:

Company Code.

Tolerance Group: Enter a unique identifier.

Limits: Specify amount or percentage limits.

3. Save.

Tolerance Group for Users (OBA3)

Explanation:

Assign tolerance groups to specific users.

1. Enter OBA3 in the command field.

2. Assign:

User ID.

Tolerance Group.

3. Save.

Tolerance Group for G/L Accounts (OBA0)

Explanation:

Sets transaction limits for specific G/L accounts.

1. Enter OBA0 in the command field.

2. Define:

Company Code.

Account: Specify the G/L account.

Limits: Set maximum posting amounts.

3. Save.

Maintain Controlling Area (OKKP)

Explanation:

Defines the controlling area for cost accounting and reporting.

1. Enter OKKP in the command field.

2. Define:

Controlling Area: Enter a unique identifier.

Currency: Define the controlling area currency.

Fiscal Year Variant: Link the fiscal year variant.

3. Save.

Assign Company Code to Controlling Area (OX19)

Explanation:

Links the company code to its controlling area for cost reporting.

1. Enter OX19 in the command field.

2. Assign:

Company Code.

Controlling Area.

3. Save.

Maintain Global Parameters (OBY6)

Explanation:

Global parameters control key company code settings like fiscal year and currency.

1. Enter OBY6 in the command field.

2. Configure:

Company Code.

Settings: Fiscal Year Variant, Chart of Accounts, etc.

3. Save.

Deactivate Document Splitting (SM30)

Explanation:

Document splitting in SAP is used to split accounting documents for accurate financial reporting by
segment or business area. Deactivating it is required when splitting is unnecessary.1. Enter SM30 in
the command field.

1. Enter SM30 in the command field.

2. Enter Table/View Name: V_SPLIT_ACTIV.

3. Click Maintain.

4. Select the Company Code and uncheck the Active field.

5. Save.

SM12 - Unlock Entries

Explanation:

This transaction is used to unlock entries that are locked due to an incomplete or interrupted
transaction process. This is typically done when a user session is left open, and no data entry is being
made.

1. Enter SM12 in the command field.

2. Click Execute (or press F8).

3. In the User Name field, enter the SAP user whose locks you want to view or release.

4. Select the entries that are locked (they will be shown in the list).

5. To release a lock, select the entries you want to unlock and click Delete (or unlock).

6. Confirm the action when prompted.

OB16 - Check Field Lengths of Sort Key

Explanation:

This configuration allows you to check and configure the field lengths of the sort key for certain
transactions, ensuring consistency in data processing and reporting.

1. Enter OB16 in the command field.

2. The screen displays a list of sort keys.

3. You can view the field length of each sort key used in transaction processing.

4. You can select a sort key to view its specific details, such as the field length and related
configurations.

5. No changes are required unless you want to modify the sort key (this can be done through the
Change button).

OBR2 - Delete Transactional Data

Explanation:

This T-code is used to delete transactional data (financial transactions, journal entries, etc.) from SAP.
This action is typically required when clearing up unnecessary data or performing data archiving.
1. Enter OBR2 in the command field.

2. Specify the Company Code or the range of company codes for which you wish to delete
transactional data.

3. Enter additional criteria, such as the fiscal year or posting period, if necessary.

4. Click Execute.

5. A confirmation prompt will appear, confirming that the data will be permanently deleted.

6. Click Yes to confirm and delete the data.

OB22 - Check Local Currencies Assigned to Company

Explanation:

This transaction allows you to check the local currencies assigned to a company code for accurate
financial reporting and transactions in the respective local currency.

1. Enter OB22 in the command field.

2. The system will display a list of company codes and their corresponding local currencies.

3. You can view and verify the local currency assigned to each company code.

4. To make changes, select the company code and edit the local currency field if required.

5. Save the changes if any.

MASS- Mass Changes in G/L Master Data Fields

Explanation:

The MASS transaction allows you to perform mass changes to G/L master data fields, such as Field
Status Groups (FSG) and other G/L attributes, across multiple accounts or company codes.

1. Enter MASS in the command field.

2. Choose Object Type (e.g., G/L Accounts).

3. Specify the fields you want to change (e.g., Field Status Group).

4. Enter the criteria for the G/L accounts you want to change (e.g., company codes, account
numbers).

5. Click Execute.

6. The system will display a list of accounts matching the criteria. Select the accounts you wish to
modify.

7. After selecting, choose the New Value for the field (e.g., new Field Status Group).

8. Click Save to apply the mass changes.

OBH2 - Copy Number Ranges from Fiscal Year (One Year to Another Year)

Explanation:

This transaction is used to copy number ranges for documents from one fiscal year to another. It
ensures that number ranges are consistent across different fiscal years.

1. Enter OBH2 in the command field.

2. In the Source Fiscal Year field, enter the fiscal year from which the number ranges will be copied.
3. In the Target Fiscal Year field, enter the fiscal year to which the number ranges will be copied.

4. Click Execute.

5. The system will display the number ranges from the source fiscal year and allow you to copy them
to the target fiscal year.

6. Click Save to finalize the process.

Here are the additional notes and explanations based on the new inputs:

1. BNKA (Table) – To See the Created Bank Details

Purpose:

The BNKA table stores details of the bank master data, including bank keys, bank accounts, and other
related information.

Steps:

1. Go to Transaction Code: SE16N (Data Browser).

2. Enter Table Name: BNKA.

3. Enter Filter Criteria (if needed):

o For example, enter a specific Bank Key or Country to filter.

4. Execute the transaction to display the bank details stored in BNKA.

This table will show the bank keys, bank accounts, and the corresponding country. You can also
search for bank-specific information such as house banks and bank accounts.

2. AL11 – To See the DMEE Downloaded Files

Purpose:

AL11 is used to view the files stored on the application server, including the DMEE (Data Medium
Exchange) files, which are used in electronic payment processing (e.g., in the DME or EDI payment
method).

Steps:

1. Go to Transaction Code: AL11.

2. Navigate to the Directory Path:

o In the Directory field, enter the path where the DMEE files are stored (e.g.,
/usr/sap/<SID>/DVEBMGS<xx>/data).

3. Execute the transaction.

4. View Files: You can now see the DMEE downloaded files, which include payment files
generated during the automatic payment program (e.g., DME or EDI files).

This is helpful for monitoring the payment files created during the execution of the automatic
payment program, especially for bank transfer payments.
GENERAL LEDGER:
FS00 - GL Account Creation

1. Go to T-Code FS00.

2. Enter the GL Account Number and Chart of Accounts.

3. Choose Create (if creating a new GL) or Change.

4. Fill in details like Account Group, Control Data, Field Status Group, and Currency.

5. Save the GL account.

F.10 - Display Created GLs

1. Use T-Code F.10.

2. Enter the Chart of Accounts and specify filters if needed.

3. Execute the report to see a list of GL accounts.

FS04 - Display Changes Made to GL

1. Go to T-Code FS04.

2. Enter the GL Account and Chart of Accounts.

3. Execute to view a detailed log of changes (e.g., who changed it, what was changed).

FB50 - GL Posting Without Posting Key

1. Use T-Code FB50.

2. Enter the Header Data (Document Date, Posting Date, Document Type).

3. In the line items, specify GL Accounts, Amounts, and additional details like Cost Centres.

4. Save or Post.

F-02 / FB01 - GL Posting with Posting Key

1. Use T-Code F-02 or FB01.

2. Enter the Header Data.

3. Specify Posting Keys, GL Accounts, and Amounts in line items.

4. Save or Post.

OB41 - Field Status Group Maintenance

Purpose: To define the field status (mandatory, optional, or suppressed) for GL postings at the
posting key level.

1. Use T-Code OB41.

2. Select the Posting Key to configure.

3. Modify the field status settings as required.

4. Save your changes.

FB03 - Display GL Document

1. Use T-Code FB03.

 2. Enter the Document Number, Fiscal Year, and Company Code.

3. Execute to display the document.

4. If the Document Number is unknown, use the Document List option.

FB02 - Change GL Document

1. Use T-Code FB02.

2. Enter the Document Number and open the document.

3. Click on the line item to edit the details.

4. Save the changes.

F.01 - Financial Statement

Purpose: To generate financial statements such as Profit & Loss and Balance Sheet.

1. Use T-Code F.01.

2. Enter the Company Code, Fiscal Year, and Report Format.

3. Execute to generate the report.

SE11 - ABAP Dictionary

Purpose: To view table fields and their characteristics.

1. Use T-Code SE11.

2. Enter the Table Name (e.g., BKPF).

3. View the fields, their data types, and relationships.

SE93 - T-Code Program Viewer

Purpose: To identify the program associated with a T-Code.

1. Use T-Code SE93.

2. Enter the desired T-Code and execute.

3. View the program name linked to the T-Code.

SE38 - Program Code Viewer

Purpose: To view the ABAP code for a specific program.

1. Use T-Code SE38.

2. Enter the Program Name (e.g., associated with a T-Code).

3. Open and view the code.

SE16N - Table Data Viewer

Purpose: To view raw data in SAP tables.

1. Use T-Code SE16N.

2. Enter the Table Name (e.g., BKPF, BSEG).

3. Specify filters if required and execute.

4. View the table data.

Important Tables
BKPF: Stores accounting document header data (e.g., document type, date, company code).

BSEG: Stores line-item details for accounting documents (e.g., GL accounts, amounts).

SKA1: Contains GL master data at the Chart of Accounts level.

SKB1: Contains GL master data at the Company Code level.

SKAT: Contains GL master data descriptions at the Central level.

Sample Document
1. FBN1 - Create Number Range for Sample Document (X2)

1. Enter FBN1 in the SAP command field.

2. In the Document Type field, select or enter X2 for the sample document type.

3. Set the number range (e.g., from 100000 to 199999).

4. Save the configuration.

Explanation: This step defines a unique number range for the X2 document type. Each document
created with this type will automatically get a unique document number within this range. This
ensures no conflict with otherwise document types.

2. F-01 / FBM1 - Create Sample Document

Purpose: Create a Sample Document for later use or as a template for posting.

1. Enter FBM1 (or F-01) in the SAP command field.

2. In the Document Type field, enter SA.

3. Enter the Company Code, Posting Date, and Document Date.

4. Add the line items such as debit or credit entries for the relevant GL accounts.

For example: Debit Prepaid Rent (GL Account: 123000), Credit Bank (GL Account: 100000).

5. Save the document to create the sample.

Explanation: FBM1 or F-01 is used to create a Sample Document. This document can later be used
for reference or as a template for posting similar transactions.

3. FBM2 - Change Sample Document

1. Enter FBM2 in the SAP command field.

2. Enter the Document Number of the sample document that you wish to modify.

3. Make the necessary changes, such as modifying line items, amounts, or the GL accounts
involved.

4. Click Save to update the document.

Explanation: FBM2 is used to modify an existing sample document when adjustments are required.
This is typically used when an error was made during the initial creation or if the document needs to
be updated.

4. FBM3 - Display Sample Document

 1. Enter FBM3 in the SAP command field.

2. Enter the Document Number to view a sample document.

3. Click Enter to display the document details, including line items, amounts, and accounting data.

Explanation: FBM3 is used to display a sample document that has been created or posted in the
system. This allows users to review the document details before or after posting.

5. F.57 - Delete Sample Document

1. Enter F.57 in the SAP command field.

2. Enter the Document Number of the sample document you wish to delete.

3. Click Execute to confirm the deletion.

4. SAP will ask for confirmation; once confirmed, the document will be deleted.

Explanation: F.57 is used to delete a document if it was created in error or is no longer needed. Be
cautious, as this action permanently removes the document from the system.

6. FB01 - Post Document Using Sample Document

1. Enter FB01 in the SAP command field.

2. In the Document Type field, select SA.

3. Enter the Company Code, Posting Date, and Document Date.

4. Add the line items (e.g., debit Prepaid Rent, credit Bank) using the details from the sample
document.

5. Save the document to post it in the system.

Explanation: FB01 is used to post a document based on the sample document template that has
been created or modified. This allows users to quickly post a transaction without manually entering
all details, using the saved sample document's information.

Recurring Document
1. FBN1 - Define Number Range for Recurring Document

1. Enter FBN1 in the SAP command field.

2. Select Recurring Document Type (e.g., 'X1').

3. Enter the number range (e.g., 1000000 to 1999999) for recurring documents.

4. Save the configuration.

Explanation: This step ensures that each recurring document has a unique document number and
prevents conflicts with other document types.

2. FB01 - Post Prepaid Rent Expenses

1. Enter FB01 in the SAP command field.

2. Choose Document Type (e.g., 'SA' for standard).

3. Enter Company Code, Posting Date, and Document Date.

4. Add line items for the Prepaid Rent account (debit) and Bank account (credit).
 5. Save the document.

Explanation: This step involves posting a manual entry for prepaid rent, which will serve as the basis
for creating the recurring document template.

3. FBD1 - Create Recurring Document

1. Enter FBD1 in the SAP command field.

2. Select the Document Type (e.g., 'SA').

3. Enter the Company Code and Posting Date.

4. Enter Amount, GL accounts, and Cost Centres.

5. Define the frequency (e.g., monthly, quarterly) for the recurring posting.

6. Set the start date and end date for the recurring document.

7. Save the document.

4. FBD2 - Change Recurring Document

1. Enter FBD2 in the SAP command field.

2. Enter the Document Type and Document Number of the recurring document to be modified.

3. Make necessary changes to line items, amounts, or posting frequency.

4. Save the changes.

5. F.15 - Display Recurring Documents

1. Enter F.15 in the SAP command field.

2. Specify the Document Type (e.g., 'SA') and other filtering criteria such as the start date or end
date.

3. Execute the search to display the list of recurring documents.

6. F.56 - Delete Recurring Document

1. Enter F.56 in the SAP command field.

2. Enter the Document Type and Document Number of the recurring document to be deleted.

3. Execute the deletion.

7. F.14 - Post Documents Using Recurring Document

1. Enter F.14 in the SAP command field.

2. Select the Document Type (e.g., 'SA') and enter the Posting Period.

3. Execute the transaction to post the recurring document.

Explanation: This transaction is used to post recurring documents automatically, such as monthly
rent or depreciation entries, based on the template defined earlier.

8. SM35 - Post Document by Executing the Batch Input Session

1. Enter SM35 in the SAP command field.

2. Choose the Batch Input Session related to recurring documents (e.g., 'MONTHLY_RENT').

3. Execute the batch input session to post the documents

Purpose: To execute the selected batch input session and post the documents.

After selecting the batch input session, click the Process button in the toolbar.

A prompt will appear asking you whether to process the session in foreground or background:

Foreground: The session is processed immediately, and you can monitor its progress in real-time.

Background: The session will be processed in the background without your direct interaction. You
can check the status later.

If you choose Foreground, the system will process the session and show any errors or warnings in the
process logs.

If you choose Background, the session will be executed in the background, and you will be notified
once the process is complete.

Explanation: SM35 processes a batch of recurring documents automatically, saving time and effort in
posting large volumes of documents.

9. FB03 - Display Document Posted by Recurring Cycle

1. Enter FB03 in the SAP command field.

2. Enter the Document Number or select the document from the list.

3. Execute the transaction to view the posted document.

Park Document
T-Codes for Parking and Processing GL Documents:

FB50: Park a General Ledger document.

FBV3: Display a parked document.

FBV2: Change a parked document.

FBV0: Post a parked document.

FB08: Reverse or delete a parked document.

FBV5: Approve a parked document.

1. Open T-code: Enter FB50 in the command field to open the General Ledger document parking
screen.

2. Enter Document Details:

Document date: Enter the date when the transaction occurred.

Posting date: Enter the date for the posting (this is the date the transaction will be recorded in the
General Ledger).

Company Code: Select the company code for the document.

3. Enter Document Items:

Account: Enter the GL account numbers for each item in the document.

Amount: Enter the amount for each account.

4. Park Document:
 Instead of posting the document, click the Park button (or select "Park" from the menu) to store
the document without posting it to the General Ledger.

The document will be saved as a parked document in the system.

5. Save: The document is now saved in the system in a parked state.

Display Parked General Ledger Document

T-code: FBV3 (Display Parked Documents)

Steps:

1. Open T-code: Enter FBV3 in the command field.

2. Enter Document Number: If you know the document number, enter it in the field.

3. Search for Parked Documents: If the document number is unknown, use search parameters like
the company code, document type, posting date, etc.

4. Display Document: Once the document appears, click on the document number to display the
document details.

The screen will show all the details of the parked GL document (accounts, amounts, tax codes,
etc.).

You can review the document and decide if further changes are needed or if it should be posted.

Change Parked General Ledger Document

T-code: FBV2 (Change Parked Documents)

Steps:

1. Open T-code: Enter FBV2 in the command field.

2. Enter Document Number: Enter the document number of the parked document you want to
change.

3. Make Changes:

Change amounts, accounts, or add new line items as necessary.

Modify other details like cost centres or tax codes if required.

4. Save: After making changes, click Save to store the updated parked document. The document
remains in the parked state.

Post Parked General Ledger Document

T-code: FBV0 (Post Parked Documents)

Steps:

1. Open T-code: Enter FBV0 in the command field.

2. Enter Document Number: Enter the document number of the parked document you want to post.

3. Review Document:

The system will display the parked document.

Review the details to ensure everything is correct.

4. Post Document:
 Click the Post button to move the document from the parked state to the posted state.

The document is now part of the official General Ledger and cannot be changed unless reversed.

Reverse or Delete Parked General Ledger Document

T-code: FB08 (Reverse Document)

Steps:

1. Open T-code: Enter FB08 in the command field.

2. Enter Document Number: Enter the document number of the parked document you wish to
reverse.

3. Reversal Reason: Enter a reason for the reversal (optional).

4. Reverse: Click Reverse to delete or reverse the parked document. This action removes the parked
document from the system.

Parked General Ledger Document

T-code: FBV5 (Approve Parked Document)

Steps:

1. Open T-code: Enter FBV5 in the command field.

2. Enter Document Number: Enter the parked document number that needs approval.

3. Approve:

Review the parked document.

If everything is correct, approve it. This step is typically used in scenarios where documents require
managerial or supervisory approval before posting.

4. Post: Once the document is approved, it can be posted using FBV0.

Parked General Ledger Document: A document stored temporarily in SAP without being posted to
the General Ledger. This allows for review and editing before it is finalized.

Posting: The act of recording a document permanently in the General Ledger. Once posted, the
document becomes part of the official financial records.

Approval: Some organizations implement an approval process for parked documents to ensure that
all documents are reviewed before posting.

Held Document
A held document is used to save incomplete or temporary financial transactions. Unlike parked
documents, held documents are not assigned a document number and are primarily used for drafts
or for transactions requiring additional information before being finalized.

Key T-Codes for Held Documents

1. F-02: General Journal Entry - Create a held document for GL entries.

2. FB50: Enter GL Account Document - Hold GL account documents in a simplified format.

3. FB11: Post held documents after review.

Steps to Hold a Document

Step 1: Create a Document

1. Use T-Code: F-02 or FB50 to start creating a journal entry.

2. Enter the following details:

- Document Date: Date of the transaction.

- Posting Date: The financial period date.

- Document Type: E.g., SA for journal entries.

- GL Accounts and Amounts: Input line-item details for debit and credit.

- Cost centre or Profit centre: If applicable.

Step 2: Save as Held Document

1. Instead of posting or parking, click on "Hold" in the toolbar.

2. Provide a temporary name or identifier for the held document.

3. The system will save the document as held without assigning a document number.

Steps to Retrieve and Post a Held Document

Step 1: Retrieve the Held Document

1. Use the same T-Code where the document was held (e.g., F-02 or FB50).

2. On the initial screen, click "Held Document" from the menu.

3. Enter the temporary identifier (if known) or browse through the list of held documents.

Step 2: Review and Modify (if needed)

1. Check the details for accuracy.

2. Make changes if necessary.

Step 3: Post the Document

1. Click "Post" to finalize the document.

2. The system will assign a permanent document number, and the entry will reflect in the General
Ledger.

Key Features and Benefits of Held Documents

1. Temporary Storage: Save incomplete documents without impacting accounting data.

2. Flexibility: Modify or delete held documents without any restrictions.

3. No Impact on Reports: Held documents do not appear in reports or financial statements.

4. Error Prevention: Prevents accidental posting of incomplete or incorrect entries.

Pre-Requisites of Document Reversal

FBN1 - Maintain Reverse Document & Number Ranges

Explanation:
The FBN1 transaction is used to maintain the reverse document number ranges and manage reversal
document handling in SAP. This is critical for processing and tracking reversed documents accurately
in the system.

1. Enter FBN1 in the command field.

2. Select the Company Code for which you want to maintain reverse number ranges.

3. Define the Number Range for reverse documents.

4. Specify the Document Type for which the reversal applies.

5. Enter the From and to values for the document number range.

6. Save the changes.

Define Reason for Reversal (SPRO)

Explanation:

The reversal reason defines the reason for reversing a financial transaction, and it is set up in SAP
under the customizing section.

Path:

SPRO → Financial Accounting (New) → General Ledger (New) → Business Transactions → Adjustment
Posting/Reversal → Define Reason for Reversal

1. Choose Define Reason for Reversal.

2. Click New Entries to create a new reason for reversal.

3. Provide a Reason Code (e.g., 01), Description (e.g., Error Correction), and any additional necessary
details.

4. Save your changes.

FB08 - Individual Reversal

Explanation:

The FB08 transaction is used to reverse individual financial documents. This is commonly used for
correcting posting errors or reversing documents in the general ledger.

1. Enter FB08 in the command field.

2. In the Document Number field, enter the number of the document you want to reverse.

3. Enter the Company Code and Fiscal Year.

4. If needed, select a Reason for Reversal (configured in SPRO).

5. Click Post to reverse the document.

6. The system will create a reversing document with the opposite entries to the original one.

F.80 - Mass Reversal

Explanation:

The F.80 transaction allows you to perform mass reversals, making it easier to reverse multiple
documents at once, particularly useful in large-scale data processing.

1. Enter F.80 in the command field.

2. Select Mass Reversal.

3. You can enter criteria to select the documents to reverse, such as Document Type, Company Code,
Posting Date, etc.

4. You can select the Test Run option first to simulate the reversal without making changes.

5. After checking the simulation, execute the Mass Reversal process.

6. The system will generate the reversal documents for the selected entries.

FB03 - GL Document Display

Explanation:

The FB03 transaction allows you to display a specific General Ledger (GL) document. It helps you
view the details of any posted document, such as line items, amounts, and related data.

1. Enter FB03 in the command field.

2. Enter the Document Number, Company Code, and Fiscal Year.

3. Click Enter.

4. The document details will be displayed, including all line items, amounts, and related information.

FAGLB03/FS10N - GL Account Balance Display

Explanation:

These transactions are used to display the balance of a General Ledger account, including details on
balances, and posted transactions.

1. Enter FAGLB03 or FS10N in the command field.

2. Enter the G/L Account and Company Code.

3. You can filter by Period and Fiscal Year for detailed reporting.

4. Click Execute.

5. The system will display the account balance, with details on debits, credits, and the closing
balance.

FBL3N - GL Account Line Items Display

Explanation:

FBL3N allows users to display line items for General Ledger accounts. It is particularly useful when
you need to analyse individual transactions that make up the balance of a GL account.

1. Enter FBL3N in the command field.

2. Enter the G/L Account and Company Code.

3. Specify the Document Number Range and Posting Period if needed.

4. Click Execute.

5. The system will display a list of line items for the selected account.

Open Item Display- BSIS & Cleared Item Display- BSAS

Enter the transaction code SE16N in the SAP command field and press Enter.

Type BSIS for open items or BSAS for cleared items in the Table Name field.

Press Enter or click Execute.

Set Selection Criteria:

Enter specific filters to narrow down your data, such as:

BELNR (Document Number): Input the document number or range.

BUKRS (Company Code): Enter the company code.

HKONT (G/L Account): Specify the G/L account.

BUDAT (Posting Date): Define a date or range.

WRBTR (Amount): Enter specific amounts or ranges.

Leave fields blank to view all entries in the table (not recommended for large datasets).

Execute the Query:

Click the Execute button (F8) to display the results.

Analyse the Data:

Review the table entries, focusing on document numbers, G/L accounts, amounts, and clearing
status.

For BSIS, only open items appear.

For BSAS, cleared items with clearing documents and dates are shown.

Cross-Check (Optional):

Use FBL3N or FB03 to validate the retrieved data against G/L line items or individual documents.

F-07 - Outgoing Payments (Clearing Open Items)

Explanation:

The F-07 transaction is used for clearing open items in accounts payable, such as outgoing payments
for vendors.

1. Enter F-07 in the command field.

2. Specify the Vendor, Company Code, and Payment Amount.

3. Select the open items that need to be cleared (usually through Document Number or
Customer/Vendor).

4. Confirm the payment details and click Post to make the payment and clear the items.

F-06 - Incoming Payments (Clearing Open Items)

Explanation:

F-06 transaction is used to clear open items related to incoming payments for customers.

1. Enter F-06 in the command field.

2. Enter the Customer, Company Code, and Payment Amount.

3. Select the open items you want to clear (by Document Number or Customer/Vendor).

4. Confirm the payment and click Post to clear the items and record the incoming payment.
PARTIAL AND RESIDUAL PAYMENTS
Scenario Overview:

1. Post a rent expense of 500 to the Outstanding Rent Account using T-Code FB50.

2. Pay a portion (250) using T-Code F-07 with the residual balance of 250 left.

Step 1: Post Rent Using FB50

1. Access Transaction FB50:

o Enter T-Code FB50 in the command field.

2. Enter Header Data:

o Document Date: Current or transaction date.

o Posting Date: Date the entry is posted.

o Company Code: E.g., RG18.

o Currency: Enter the transaction currency (e.g., USD).

3. Enter Line Items:

o Line Item 1:

 GL Account: Rent Expense Account (e.g., 400500).

 Debit Amount: 500.

 Cost Centre/Business Area: Add if required for controlling purposes.

o Line Item 2:

 GL Account: Outstanding Rent Account (e.g., 300200).

 Credit Amount: 500.

4. Check and Post:

o Click Simulate to verify the entry.

o If everything is correct, click Post.

Step 2: Pay 250 Using F-07 with Residual Balance

Access F-07:

1. Enter T-Code F-07 in the command field.

Enter Header Data:

1. Fill in the following:

o Document Date: Current or transaction date.

o Posting Date: Date the payment is posted.

o Company Code: E.g., RG18.

o Document Type: KZ (Vendor Payment) or DZ (Customer Payment).

o Currency: Enter the transaction currency.

Enter Line Items:

1. Line Item 1: Record the Payment:

o GL Account: Bank Account (e.g., 100000).

o Debit Amount: 250.

2. Line Item 2: Offset the Outstanding Rent:

o GL Account: Outstanding Rent Account (e.g., 300200).

o Credit Amount: 250.

Process Open Items:

1. Click Process Open Items or press Ctrl+F8.

o The system displays the open item for the outstanding rent.

2. Select the open item and adjust the payment:

o Enter 250 in the Residual Payment field.

o The system automatically calculates the remaining balance (250).

Post the Document:

1. Click Post to save the payment.

o The system clears the payment amount and creates a new open item for the residual
balance (250).

Verification:

1. FB03:

o Use this T-Code to display the posted documents for verification.

2. FBL3N:

o Check the Outstanding Rent GL account to ensure:

 The original amount is reduced by 250.

 A new open item for 250 is created (residual amount).

Post Rent to Outstanding Rent Account and Make Partial Payment Using F-07

Step 1: Post Rent Using FB50

1. Access Transaction FB50:

o Enter T-Code FB50 in the SAP command field.

2. Enter Header Data:

o Document Date: Current or transaction date.

o Posting Date: Date the entry is posted.

o Company Code: E.g., RG18.

 o Currency: Enter the transaction currency (e.g., USD).

3. Enter Line Items:

o Line Item 1:

 GL Account: Rent Expense Account (e.g., 400500).

 Debit Amount: 500.

 Cost Centre/Business Area: Add if required.

o Line Item 2:

 GL Account: Outstanding Rent Account (e.g., 300200).

 Credit Amount: 500.

4. Check and Post:

o Click Simulate to verify the entry.

o If everything is correct, click Post.

Step 2: Make Partial Payment Using F-07

Partial Payment keeps the original open item open with a reduced balance, showing the payment
separately.

1. Access F-07

 Enter T-Code F-07 in the command field.

2. Enter Header Data

1. Fill in the following fields:

o Document Date: Current or transaction date.

o Posting Date: Date the payment is posted.

o Company Code: E.g., RG18.

o Document Type: KZ (Vendor Payment) or DZ (Customer Payment).

o Currency: Enter the payment currency.

3. Enter Line Items

1. Line Item 1: Record the Payment:

o GL Account: Bank Account (e.g., 100000).

o Debit Amount: 250.

2. Line Item 2: Offset the Outstanding Rent:

o GL Account: Outstanding Rent Account (e.g., 300200).

o Credit Amount: 250.

4. Process Open Items

1. Click Process Open Items or press Ctrl+F8.

o The system displays the open item for the outstanding rent (500).

2. Select the open item and adjust the payment:

o Enter 250 in the Partial Payment field.

o The system leaves the original open item for 500 and adds a new open item for 250.

5. Post the Document

1. Click Post to save the partial payment.

Verification

1. FB03:

o Use this T-Code to display the posted documents for verification.

2. FBL3N:

o Check the Outstanding Rent GL account to ensure:

 The original item (500) is still open.

 A new open item for the partial payment (250) is created.

Activating Open Item Management After Posting

Reverse Existing Entries

Before activating Open Item Management, reverse any previously posted transactions in the G/L
account.

T-Code: FB08 (Individual Reversal) or F.80 (Mass Reversal).

1. Enter the Document Number to reverse.

2. Choose the Reversal Reason (e.g., "Reversal of Open Item activation").

3. Execute the reversal.

Activate Open Item Management

T-Code: FAGL_ACTIVATE_OP

1. Company Code: First, enter the Company Code for which you want to activate Open Item
Management.

2. G/L Account: Input the G/L Account number.

3. Document Type: Choose the Document Type associated with this G/L account.
 4. Perform Posting: Check the Perform Posting box if you want to automatically post the
activation.

5. Execute in Background: In the menu, choose Program → Execute in Background.

6. Output Device: Enter LP01 (or your default printer).

7. Immediate Execution: Choose Immediate execution and then Save.

Verify Activation in FS00

T-Code: FS00 (G/L Account Master Data).

1. Enter the G/L Account and select Display.

2. Go to the Control Data tab and confirm that the Open Item Management checkbox is selected,
indicating the activation was successful.

Enable Line-Item Display After posting

Select Line-Item tick box

T-Code: FS00 (G/L Account Master Data).

1. Enter the G/L Account.

2. In the Control Data tab, tick the box for Line-Item Display.

3. Save the changes.

Block the G/L Account

Before running the activation, block the G/L account to avoid any new postings while activation
takes place.

T-Code: FS00 (G/L Account Master Data).

1. Enter the G/L Account and select Change.

2. In the Control Data tab, select the Block for Posting checkbox.

3. Save the changes.

Run the Program for Line-Item Activation

T-Code: SE38.

1. Enter the program name RFSEPA01 and click Execute.

2. Follow the prompts and execute the program. This will ensure that the line items are activated
for the G/L account.

Verify Line Items in BSIS Table

T-Code: SE16N (Table Browser).

1. Enter BSIS (for open items) or BSAS (for cleared items) in the Table Name field.

2. Use Filters (e.g., G/L Account, Document Type) to view line-item data.

3. Execute the query and confirm if line items are now available.

Unblock the G/L Account

T-Code: FS00 (G/L Account Master Data).

 1. Return to the G/L Account and select Change.

2. Unblock the account by unchecking the Block for Posting checkbox.

3. Save the changes.

ACCOUNTS PAYABLE
1. OBD3 – Define Vendor Account Groups with Screen Layout (Vendors)

Purpose:

Vendor account groups classify vendors (e.g., Domestic, Foreign) and determine the screen layout
during the creation of vendor master data.

Steps:

1. Go to Transaction Code: OBD3.

2. Click on New Entries.

3. Enter the following details:

o Account Group: Create account groups like Z100 (Domestic Vendors) or Z200
(Foreign Vendors).

o Description: Provide a meaningful description for the account group (e.g., "Domestic
Vendors" or "Foreign Vendors").

4. Double-click on Company Code Data:

o Under Account Management, select Reconciliation Account as Required.

o Adjust other fields as necessary, like Sort Key, Payment Terms, etc.

5. Save the entries.

2. XKN1 – Create Number Ranges for Vendor Accounts

Purpose:

Number ranges ensure that vendor accounts have unique identifiers, preventing duplication.

Steps:

1. Go to Transaction Code: XKN1.

2. Click on Change Intervals.

3. Define the number range:

o Number Range Name: Assign a name to the range (e.g., Z1, Z2).

o From Number: Specify the starting number (e.g., 100000).

o To Number: Specify the ending number (e.g., 199999).

4. Save the configuration.

3. OBAS – Assign Number Ranges to Vendor Account Groups

Purpose:

Assign the created number ranges to specific vendor account groups, ensuring each group has
unique identifiers.

Steps:

1. Go to Transaction Code: OBAS.

2. Click on Position, then select the vendor account group (e.g., Z100 or Z200).

3. Assign Number Ranges:

o Assign Z1 to account group Z100,

o Assign Z2 to account group Z200.

4. Save the settings.

4. OBA3 – Define Tolerance for Customers and Vendors

Purpose:

Tolerance limits help manage differences in payment amounts, allowing the system to accept certain
deviations.

Steps:

1. Go to Transaction Code: OBA3.

2. Click on New Entries.

3. Enter the following details:

o Company Code: Specify the company code for which the tolerance group will apply.

o Tolerance Group: Create a name (e.g., VEND).

o Maximum Payment Difference: Define the maximum permissible

over/underpayment limit.

o Maximum Cash Discount: Specify the maximum allowed cash discount.

4. Save the configuration.

5. OBA7 – Maintain Vendor Document Types and FBN1 – Number Ranges

Purpose:

Define the document types for vendor transactions and assign number ranges for proper document
tracking.

Steps (OBA7):

1. Go to Transaction Code: OBA7.

2. Review the Standard Document Types: These document types are used for different vendor
transactions:

o KR: Vendor Invoice,

o KG: Vendor Credit Memo,

 o KZ: Vendor Payment,

o KA: Vendor Advance.

3. Save the configuration.

Steps (FBN1):

1. Go to Transaction Code: FBN1.

2. Define Number Ranges for the vendor document types (e.g., for KR, KG).

3. Save the number ranges.

6. Create Raw Material Account in FS00

Purpose:

Create a General Ledger (GL) account for raw materials used in inventory management.

Steps:

1. Go to Transaction Code: FS00.

2. Create a GL Account for raw materials:

o Account Type: Balance Sheet,

o Account Group: Raw Materials,

o Field Status Group: Assign an appropriate field status group (e.g., RAWM).

3. Save the GL account.

7. Create Accounts Payable Reconciliation Account in FS00

Purpose:

Create a vendor reconciliation account to manage accounts payable liabilities.

Steps:

1. Go to Transaction Code: FS00.

2. Create the Accounts Payable Reconciliation Account:

o Account Type: Balance Sheet,

o Reconciliation Account: For vendors,

o Sort Key: 012 (to control document entry order),

o Field Status Group: G067.

o Do NOT select "Only Balances in Local Currency".

3. Save the reconciliation account.

8. XK01 – Create Vendor Master Data at Central Level

Purpose:
Create and maintain vendor master data for use across multiple company codes in the organization.

Steps:

1. Go to Transaction Code: XK01.

2. Enter Vendor Master Data:

o General Data: Vendor name, address, contact details, and bank information,

o Company Code Data:

 Reconciliation Account: Specify the accounts payable account (e.g., 210000),

 Sort Key: 012,

 Payment Terms: Standard terms like 0001,

 Cash Management Group: A1 (if applicable).

3. Save the vendor master data.

9. XK02 – Change Vendor Master Data, XK03 – Display Vendor Master Data

Purpose:

Modify and display existing vendor data in the system.

Steps:

 XK02: To change vendor master data if any modifications are needed.

 XK03: To display vendor master data and check the vendor's details.

10. Vendor Master Data Tables

Purpose:

Know the SAP tables where vendor master data is stored for efficient data retrieval.

Tables:

 LFA1: Stores general data related to the vendor,

 LFB1: Stores company code-specific vendor data,

 LFM1: Stores vendor data related to purchasing.

11. FB60 – Vendor Invoice Posting, F-43 – Vendor Invoice with Posting Keys

Purpose:

Post vendor invoices and related transactions to the accounts payable system.

Steps (FB60):

1. Go to Transaction Code: FB60.

2. Enter the following details:

o Vendor: Select the vendor,

 o Invoice Date: Specify the invoice date,

o Amount: Enter the invoice amount,

o Tax Code: Assign the correct tax code,

o Reconciliation Account: Specify the accounts payable reconciliation account.

3. Save the transaction.

Steps (F-43):

1. Go to Transaction Code: F-43.

2. Enter the vendor invoice details using posting keys:

o Posting Key 40 for debit (Invoice entry),

o Posting Key 31 for credit (Account payable entry).

3. Save the invoice.

12. OBB8 – Payment Terms Configuration

Purpose:

Define payment terms for vendor transactions, allowing for standardized payment schedules.

Steps:

1. Go to Transaction Code: OBB8.

2. Define Payment Terms by selecting the relevant Document Date for payments.

13. FB03 – Document Display, FK10N – Vendor Balance Display, FBL1N – Vendor Line-Item Display

Purpose:

Review vendor transaction documents and balances.

Steps:

 FB03: To display vendor document details. Initially, the system will show subledger entries;
switch to the general ledger view for main ledger entries.

 FK10N: To view vendor balances for a specified period.

 FBL1N: To display vendor line items, which can be open, cleared, or all items (based on the
selection).

14. FB65 – Vendor Credit Memo

Purpose:

Vendor credit memo is used to reverse or adjust the amount of a vendor's invoice when the vendor
has granted a credit for returned goods or services.

Steps:

1. Go to Transaction Code: FB65.

 2. Enter the details:

o Vendor: Select the vendor from whom the credit memo is issued,

o Credit Memo Amount: Enter the amount being credited,

o Reconciliation Account: Specify the accounts payable reconciliation account,

o Document Date: Enter the date of the credit memo.

3. Save the document.

15. Vendor Outgoing Payment – Manual Payment and Automatic Payment Program

Purpose:

Vendor payments can be made manually or through an automated payment program. Both methods
have different processes for generating payment transactions.

Types of Payment:

 A) Manual Payment: A manual check is created for payment to a vendor.

 B) Automatic Payment Program: The system processes payments automatically based on

payment proposals and can use either of the following two methods:

o I) Check Payment: The system prints a check to send to the vendor.

o ii) Bank Transfer: This payment type has two variations:

 DME (Data Medium Exchange): Creates a payment file and sends it to the
house bank for processing.

 EDI (Electronic Data Interchange): Creates an IDoc and sends the payment
details to the house bank electronically.

16. FI12 – Creation of House Bank

Purpose:

A house bank is created to manage the organization’s bank accounts for processing outgoing and
incoming payments.

Steps:

1. Go to Transaction Code: FI12.

2. Create a House Bank:

o Bank Key: Enter the bank key for your house bank,

o Bank Account: Specify the relevant bank account details,

o Bank Country: Enter the country where the bank is located.

3. Save the house bank data.

17. FCHI – Cheque Lot Creation

Purpose:
Create a cheque lot, which is a collection of checks that will be issued to vendors as part of the
manual payment process.

Steps:

1. Go to Transaction Code: FCHI.

2. Create Cheque Lot:

o Cheque Lot: Assign a name for the cheque lot,

o Bank Key: Select the house bank used for issuing checks,

o Cheque Numbers: Specify the range of check numbers to be used.

3. Save the cheque lot.

18. F-53 – Vendor Outgoing Payment

Purpose:

This transaction is used to post a payment to a vendor, either manually or through a payment
method like a cheque or bank transfer.

Steps:

1. Go to Transaction Code: F-53.

2. Enter the following details:

o Vendor: Select the vendor to whom the payment is being made,

o Payment Amount: Enter the payment amount,

o Bank Account: Select the bank account for the payment,

o Document Date: Specify the date of the payment.

3. Save the transaction.

19. FCH5 – Manual Check Creation, FCH6 – Check Encashment

Purpose:

These transactions are used to handle manual check creation and check encashment, respectively.

Steps (FCH5):

1. Go to Transaction Code: FCH5.

2. Enter Check Details:

o Vendor: Select the vendor,

o Check Amount: Enter the check amount,

o Cheque Number: Specify the check number.

3. Save the check details.

Steps (FCH6):

1. Go to Transaction Code: FCH6.

 2. Process Check Encashment: When the check is encashed by the vendor, enter the check
details to mark the payment as cleared.

3. Save the encashment details.

20. FCHN – Check Register

Purpose:

The check register displays all checks that have been issued, their status (encashed, voided, etc.), and
related information.

Steps:

1. Go to Transaction Code: FCHN.

2. Display Check Register: The system will show the status of checks issued, including those
that have been encashed or voided.

21. FCH3 – Check Void without Reversing the Entry Before Encashment, FCH9 – Check Void after
Encashment

Purpose:

These transactions allow you to void checks before or after they have been encashed.

Steps (FCH3):

1. Go to Transaction Code: FCH3.

2. Void Uncashed Check: Select a check that was not encashed and void it without reversing
the original accounting entry.

3. Save the voided check details.

Steps (FCH9):

1. Go to Transaction Code: FCH9.

2. Void Encashed Check: If a check has been encashed, you can void it and stop payment to the
vendor (e.g., in cases of signature mismatch, stolen checks, or text mismatch).

3. Inform the Bank: After voiding, inform the bank to stop the payment.

4. Save the voided check entry.

22. FCHV – Define Check Void Reason

Purpose:

Define reasons for voiding checks to maintain a record of why a check was voided (e.g., insufficient
funds, wrong payee).

Steps:

1. Go to Transaction Code: FCHV.

2. Enter Check Void Reason: Define the reasons for voiding checks (e.g., "Insufficient Funds",
"Wrong Payee", "Stolen Check").
 3. Save the void reason.

23. FCH8 – Check Void with Reversal of Payment Document (Insufficient Funds)

Purpose:

This transaction is used to void checks and reverse the associated payment document, especially in
case of insufficient funds.

Steps:

1. Go to Transaction Code: FCH8.

2. Select the Check to Void: Choose the check that needs to be voided due to issues like
insufficient funds.

3. Click on Cancel Payment: Reversal of the payment document occurs after voiding the check.

4. Save the transaction.

24. FCH3 – Voiding of Unissued Checks (Series Damaged or Voided)

Purpose:

Void unissued checks if the check stock is damaged, voided, or destroyed, ensuring no payment is
processed against them.

Steps:

1. Go to Transaction Code: FCH3.

2. Select Unissued Checks: Choose a range of unissued checks that need to be voided due to
damage or destruction.

3. Save the voided check details.

25. FBRA – Payment/Incoming Document Reversal

Purpose:

Reversing a payment or incoming document allows you to correct or cancel a previously posted
payment document.

Steps:

1. Go to Transaction Code: FBRA.

2. Enter Document Number and Company Code: Provide the document number and company
code for the document you want to reverse.

3. Click on Save, then select Reset and Reverse to cancel the payment.

4. Double-click to reverse the document.

26. FI01 – Creation of Bank Key

Purpose:
A bank key is needed to identify each bank in the SAP system for payment processing.

Steps:

1. Go to Transaction Code: FI01.

2. Create Bank Key:

o Bank Country: Specify the country of the bank,

o Bank Key: Enter a unique key for the bank,

o Bank Name: Enter the bank's name.

3. Save the bank key.

Open Item Management allows for the reconciliation of bank transactions (e.g., incoming, and
outgoing payments) to be tracked in the general ledger (GL). This is important for ensuring all
transactions are correctly processed and matched to the relevant vendor/customer or cash account.

27. Cash Management Group

Purpose:

Define planning groups for cash and liquidity management within the SAP Cash Management module
to better manage cash flows.

Steps:

1. Go to SPRO Path:
SPRO → FSCM → Cash and Liquidity Management → Cash Management → Master Data →
Subledger Accounts → Define Planning Groups.

2. Define Planning Groups: Create planning groups for managing cash and liquidity more
effectively.

3. Save the planning groups.

PART 1: CONFIGURING AUTOMATIC PAYMENT PROGRAM (APP)

Transaction Code: FBZP

Step 1: All Company Codes

 Purpose: Define which company codes participate in the payment program.

1. Go to FBZP > All Company Codes.

2. Enter your company code (e.g., RG18).

3. Maintain:

o Paying Company Code: e.g., RG18.

o Currency: Local or relevant currency for payments.

4. Save.
Step 2: Paying Company Codes

 Purpose: Configure payment-specific settings for the paying company code.

1. Go to FBZP > Paying Company Codes.

2. Enter the paying company code (e.g., RG18).

3. Maintain:

o Minimum Payment Amount: Set a minimum threshold (optional).

o Maximum Payment Amount: Set a maximum threshold (optional).

o Forms: Assign a form for payment advices/checks.

 For checks: Use form F110_PRENUM_CHCK.

 For payment advice: Use form F110_IN_AVIS (or country-specific).

4. Save.

Step 3: Payment Methods in Country

 Purpose: Define payment methods at the country level (e.g., bank transfer or checks).

1. Go to FBZP > Payment Methods in Country.

2. Enter the Country Code (e.g., IN for India).

3. Define:

o Payment Method Code: e.g., C for Check, T for Bank Transfer.

o Attributes:

 Payment by Check: Check this for method C.

 IBAN/Swift Required: Enable for method T.

 Enable Payment Medium for all methods.

4. Save.

Step 4: Payment Methods in Company Code

 Purpose: Assign payment methods to the company code.

1. Go to FBZP > Payment Methods in Company Code.

2. Enter the Company Code (e.g., RG18).

3. Assign:

o Payment Method: e.g., C for Check.

o House Bank: Link the house bank to the payment method.

o Required Fields: Configure partner bank type, currency restrictions, etc.

4. Save.
Step 5: Bank Determination

 Purpose: Define which banks and accounts are used for payments.

1. Go to FBZP > Bank Determination.

2. Enter your Company Code (e.g., RG18).

3. Configure:

o Ranking Order: Assign priority to house banks for payments.

o Accounts by Payment Method: Assign specific house banks and accounts for each
method (e.g., C for Check, T for Bank Transfer).

o Overdraft Limits: Optional (if required).

4. Save.

Step 6: House Bank Configuration

 Purpose: Maintain house bank details and GL account assignments.

1. Go to Transaction FI12.

2. Create House Banks:

o Assign Bank Key, Account ID, and GL Account.

o For checks: Assign Check Lots under the house bank.

 Use FCHI to define check lot number ranges.

3. Save.

PART 2: EXECUTING AUTOMATIC PAYMENT PROGRAM

Transaction Code: F110

Step 1: Access the Payment Program

1. Go to Transaction F110.

2. The system opens the Parameters screen.

Step 2: Maintain Parameters

1. Fill in the Parameters Tab:

o Run Date: Enter today’s date.

o Identification: Provide a unique code (e.g., 1223RUN).

o Company Codes: Enter the relevant company code (e.g., RG18).

o Payment Methods: Specify methods (e.g., C for Check).

o Next Posting Date: Provide the desired posting date for payment documents.
 o Documents Selection: Enter vendor/customer accounts or ranges.

2. Save.

Step 3: Proposal Run

1. Click Proposal and execute (F8).

2. Review the generated proposal:

o Check for errors (e.g., blocked invoices or missing bank details).

o Resolve errors and adjust as needed.

3. Save the proposal.

Step 4: Payment Run

1. After verifying the proposal, click Payment Run and execute (F8).

2. The system:

o Generates payment documents.

o Assigns check numbers (for checks).

o Creates payment files/forms.

Step 5: Print Checks/Payment Advice

1. Go to the Printout/Data Medium tab.

2. Configure:

o Program and Variant:

 For checks: Use RFFOUS_C (or country-specific variants).

 For payment advice: Use F110_IN_AVIS.

o Execute the print job to generate outputs.

Step 6: Transfer Files to Bank

1. If using bank transfer, download the payment file (e.g., XML or DME).

2. Upload the file to the bank portal or transfer via SAP Bank Communication Management (if
configured).

Step 7: Review the Payment Log

1. After execution, check the Payment Log for:

o Successful payments.

o Errors or failed transactions.

Step 8: Reconcile Payments

1. Reconcile vendor/customer accounts to verify clearing.

2. Monitor transactions on the bank statement for successful execution.

PART 3: FORM DETAILS

1. Form Name and Purpose:

Form Name Purpose Technology

F110_PRENUM_CHCK Pre-numbered checks SAP Script

F110_IN_AVIS Payment advice (India-specific) SAP Script

F110_US_AVIS Payment advice (US-specific) SAP Script

F110_DTA_CHCK Data Medium Exchange for payments SAP Script

2. Assign Forms to Payment Methods:

o Path in FBZP:

 FBZP > Paying Company Codes > Forms.

o Assign:

 Payment Advice Form: e.g., F110_IN_AVIS.

 Check Form: e.g., F110_PRENUM_CHCK.

PART 4: TESTING

1. Run a Test Proposal in F110 to ensure:

o Payment documents are created correctly.

o Forms are generated accurately.

2. Debug issues using SE38 logs if needed.

TIPS

 Ensure master data (vendors, customers, house banks) is complete.

 Regularly update and maintain check lots (FCHI).

 Customize forms using:

o SAP Script: SE71.

o Smart Forms: SMARTFORMS.

o Adobe Forms: SFP.

ACCOUNTS RECEIVABLE
1. OBD2 – Define Account Groups with Screen Layout (Customers)

Purpose:

Customer account groups classify customers (e.g., Domestic, Foreign) and determine the screen
layout during the creation of customer master data.

Steps:

1. Go to Transaction Code: OBD2.

2. Click on New Entries.

3. Enter the following details:

o Account Group: Create account groups like Y100 (Domestic Customers), Y200
(Foreign Customers).

o Description: Add a description, such as "Domestic Customers" or "Foreign

Customers".

4. Double-click on Company Code Data:

o Under Account Management, mark Reconciliation Account as Required.

o Adjust other fields like Sort Key, Payment Terms, etc., as needed.

5. Save the changes.

2. XDN1 – Create Number Ranges for Customer Accounts

Purpose:

Create number ranges to assign unique numbers for each customer account, ensuring no duplication.

Steps:

1. Go to Transaction Code: XDN1.

2. Click on Change Intervals.

3. Define the number range:

o Number Range Name: Assign a name for the range (e.g., Y1, Y2).

o From Number: Specify the starting number (e.g., 100000).

o To Number: Specify the ending number (e.g., 199999).

4. Save the configuration.

3. OBAR – Assign Number Ranges to Customer Account Groups

Purpose:

Assign the created number ranges to specific customer account groups.

Steps:

1. Go to Transaction Code: OBAR.

 2. Click on Position and select the customer account group (e.g., Y100, Y200).

3. Assign Number Ranges:

o Assign number range Y1 to account group Y100,

o Assign number range Y2 to account group Y200.

4. Save the settings.

4. OBA7 – Maintain Customer Document Types and FBN1 – Number Ranges

Purpose:

Define customer document types and assign number ranges to these document types.

Steps (OBA7):

1. Go to Transaction Code: OBA7.

2. Review the standard document types for customer transactions, such as:

o DR: Customer Invoice,

o DG: Customer Credit Memo,

o DZ: Customer Payment,

o DA: Customer Advance.

3. Save the document types.

Steps (FBN1):

1. Go to Transaction Code: FBN1.

2. Define Number Ranges for customer document types.

3. Save the number ranges.

5. Create Sales Account in FS00

Purpose:

Create a General Ledger (GL) account for sales revenue.

Steps:

1. Go to Transaction Code: FS00.

2. Create a GL Account for sales:

o Account Type: P&L,

o Account Group: Sales,

o Sort Key: 001,

o Field Status Group: G001.

3. Save the GL account.

6. Create Accounts Receivable Reconciliation Account in FS00

Purpose:

Create a customer reconciliation account in the general ledger for managing receivables.

Steps:

1. Go to Transaction Code: FS00.

2. Create the Accounts Receivable Reconciliation Account:

o Account Type: Asset,

o Reconciliation Account: For customers,

o Sort Key: 031,

o Field Status Group: G067.

o Do NOT select "Only Balances in Local Currency".

o Select Line-Item Display.

3. Save the reconciliation account.

7. XD01 – Create Customer Data at Central Level

Purpose:

Create and maintain customer master data centrally for use across company codes.

Steps:

1. Go to Transaction Code: XD01.

2. Enter Customer Master Data:

o General Data: Name, address, contact, and bank details,

o Company Code Data:

 Reconciliation Account: Enter the receivable account (e.g., 120000),

 Sort Key: 031,

 Payment Terms: 0001 (standard),

 Cash Management Group: A1.

3. Save the customer master data.

8. XD02 – Change Customer Master Data, XD03 – Display Customer Master Data

Purpose:

Modify and display customer data.

Steps:

 XD02: To change existing customer master data.

 XD03: To display and review customer details.

9. Customer Master Data Tables

Purpose:

Know the SAP tables where customer master data is stored.

Tables:

 KNA1: General data (customer information),

 KNB1: Company code data (customer information specific to company code),

 KNVV: Sales organization data (customer details related to sales).

10. FB70 – Customer Invoice Posting, F-22 – Customer Invoice with Posting Keys

Purpose:

Post customer invoices using specific transaction codes.

Steps (FB70):

1. Go to Transaction Code: FB70.

2. Enter the following details:

o Customer: Select the customer,

o Invoice Date: Specify the invoice date,

o Amount: Enter the invoice amount,

o Tax Code: Assign the tax code,

o Reconciliation Account: Specify the accounts receivable reconciliation account.

3. Save the transaction.

Steps (F-22):

1. Go to Transaction Code: F-22.

2. Enter the customer invoice details using posting keys:

o Posting Key 01: For debit,

o Posting Key 11: For credit.

3. Save the invoice.

11. FB03 – Document Display, FD10N – Customer Balance Display, FBL5N – Customer Line-Item
Display

Purpose:

Display customer transaction documents and balance information.

Steps:
  FB03: To display customer documents. First, the system will show the subledger entries, then
you can switch to the general ledger view to see the corresponding entries in the main
ledger.

 FD10N: To display customer balance for a specific period.

 FBL5N: To display customer line items (open, cleared, or all items).

12. FB75 – Post Customer Credit Memo

Purpose:

Post customer credit memos to reduce customer invoices.

Steps:

1. Go to Transaction Code: FB75.

2. Enter the customer credit memo details:

o Customer: Select the customer,

o Amount: Enter the credit memo amount,

o Tax Code: Assign the tax code,

o Reconciliation Account: Specify the accounts receivable reconciliation account.

3. Save the credit memo.

13. F-28 – Customer Incoming Payments

Purpose:

Post customer incoming payments to clear open items.

Steps:

1. Go to Transaction Code: F-28.

2. Enter the payment details:

o Customer: Select the customer,

o Amount: Enter the payment amount,

o Bank Account: Select the bank account from which payment is made,

o Clear Open Items: Mark the open items that are being cleared with this payment.

3. Save the payment transaction.

VENDOR IS ALSO A CUSTOMER AND CUSTOMER IS A VENDOR

1. XK01 – Create Vendor Master Data

Purpose: Create a new vendor master record for managing vendor transactions.

Steps:

1. Go to Transaction Code: XK01.

 2. Enter Vendor Number:

o Provide the vendor number (e.g., V100).

3. Enter Vendor Data:

o Reconciliation Account: Select the accounts payable reconciliation account (e.g., AP

account).

o Sort Key: Enter 012 (or as per your company's settings).

o Cash Management Group: Choose A1 (or based on your company's setup).

o Payment Terms: Select 0001 (or another payment terms if required).

4. Save the vendor master data.

2. XD01 – Create Customer Master Data

Purpose: Create a new customer master record at the central level and link the vendor to the
customer.

Steps:

1. Go to Transaction Code: XD01.

2. Enter Customer Number:

o Provide the customer number (e.g., C100).

3. Enter Customer Data:

o Under Control Data Tab, enter the vendor number to link the customer and vendor
together (e.g., link V100 with C100).

o Company Code Data:

 Reconciliation Account: Choose accounts receivable (e.g., AR account).

 Sort Key: Enter 031.

 Cash Management Group: Select A1 (as per company policy).

 Payment Terms: Select 0001.

 Check the Clearing with Vendor option to allow future clearing between the
vendor and customer.

4. Save the customer master data.

3. XK02 – Change Vendor Master Data

Purpose: Modify existing vendor data to enable clearing between the vendor and customer.

Steps:

1. Go to Transaction Code: XK02.

2. Enter Vendor Number:

o Enter the vendor number whose details you need to modify (e.g., V100).

3. Company Code Data:

 o Payment Transaction: Select the Clearing with Customers option under payment
transactions. This ensures the system allows clearing between the vendor and
customer.

4. Control Tab:

o Verify that the customer is properly linked to the vendor.

5. Save the changes to the vendor master.

4. OBA7 – Assign Number Ranges to Vendor and Customer Account Groups

Purpose: Assign number ranges to the vendor and customer account groups to maintain proper
account numbering.

Steps:

1. Go to Transaction Code: OBA7.

2. Assign Account Groups:

o Select KZ for customer accounts and DZ for vendor accounts.

o Choose the corresponding number ranges for each account group (e.g., Y1-Y2 for
vendors and X1-X2 for customers).

3. Save the configuration.

5. FB70 – Post Customer Invoice

Purpose: Record a customer invoice for the receivable.

Steps:

1. Go to Transaction Code: FB70.

2. Enter Invoice Data:

o Customer Number: Enter the customer number (e.g., C100).

o Amount: Enter the invoice amount (e.g., 1000).

o Document Date: Enter the document date.

o Tax Code: Choose the relevant tax code.

o GL Account: Select the appropriate revenue account (e.g., Sales Revenue).

3. Save the customer invoice.

6. FB60 – Post Vendor Invoice

Purpose: Record a vendor invoice for the payable.

Steps:

1. Go to Transaction Code: FB60.

2. Enter Invoice Data:

o Vendor Number: Enter the vendor number (e.g., V100).

 o Amount: Enter the invoice amount (e.g., 1000).

o Document Date: Enter the document date.

o Tax Code: Choose the relevant tax code.

o GL Account: Select the appropriate expense account (e.g., Vendor Expense).

3. Save the vendor invoice.

7. F-53 – Post Vendor Outgoing Payment

Purpose: Record the payment to the vendor.

Steps:

1. Go to Transaction Code: F-53.

2. Enter Payment Data:

o Vendor Number: Enter the vendor number (e.g., V100).

o Amount: Enter the payment amount (e.g., 1000).

o Bank Account: Select the bank account from which the payment is made.

o Payment Method: Select the payment method (e.g., Bank Transfer or Cheque).

o Clear Open Items: Mark the open items that are being cleared with this payment.

3. Save the outgoing payment.

8. F-28 – Post Customer Incoming Payment

Purpose: Record the payment received from the customer.

Steps:

1. Go to Transaction Code: F-28.

2. Enter Payment Data:

o Customer Number: Enter the customer number (e.g., C100).

o Amount: Enter the payment amount (e.g., 1000).

o Bank Account: Select the bank account where the payment was received.

o Clear Open Items: Mark the open items to be cleared with this payment.

3. Save the incoming payment.

9. FBL5N – Display Customer Line Items

Purpose: View the customer’s open and cleared items.

Steps:

1. Go to Transaction Code: FBL5N.

2. Enter Criteria:
 o Customer Number: Enter the customer number (e.g., C100).

o Document Type: Choose whether to display open or cleared items.

o Period: Specify the period to search for open items.

3. Execute the transaction to view the customer’s line items.

10. FBL1N – Display Vendor Line Items

Purpose: View the vendor’s open and cleared items.

Steps:

1. Go to Transaction Code: FBL1N.

2. Enter Criteria:

o Vendor Number: Enter the vendor number (e.g., V100).

o Document Type: Choose whether to display open or cleared items.

o Period: Specify the period for which you want to view vendor line items.

3. Execute the transaction to view the vendor’s open or cleared line items.

11. Clear Vendor and Customer Open Items

Purpose: Clear open items between the vendor and customer accounts.

Steps:

1. Go to Transaction Code: F-44.

2. Enter Vendor and Customer Data:

o Vendor Number: Enter the vendor number (e.g., V100).

o Customer Number: Enter the customer number (e.g., C100).

3. Select Open Items:

o Mark the open items between the vendor and customer accounts that need to be
cleared.

4. Clear Open Items: Ensure that both open items are cleared against each other.

5. Save the clearing document.

PAYMENT TERMS:
1. OBB8 – Create New Payment Terms

Purpose: Define new payment terms with specific credit days for vendors/customers.

Steps:

1. Go to Transaction Code: OBB8.

2. Create New Payment Term:

 o Click on New Entries to create a new payment term.

o Payment Term ID: Enter a unique ID for the payment term (e.g., Z01).

o Baseline Date Tab:

 Choose the baseline date calculation method (for example, Document Date
or Posting Date). This determines the starting point for the credit days.

o Account Type Tab:

 Select the account type for which the payment terms will apply: Vendor,
Customer, or both. This defines who will use the payment terms.

o Payment Terms Tab:

 Credit Days: Enter the number of days after which the transaction will be
considered overdue (e.g., 30 days).

 Overdue Status:

 Transactions that are within the credit days will be Not Due.

 Once the credit days are exceeded, the status will show as Overdue
in the open items.

o Default for Baseline Date:

 If No Default is selected, the user will need to manually enter the Baseline
Date during invoice posting.

3. Save the payment terms after reviewing the entries.

2. Change Payment Terms for Posted Invoices

Purpose: Modify the payment terms on posted invoices when necessary.

Steps:

 Option A: Using FB02 (Change Document):

1. Go to Transaction Code: FB02.

2. Enter Document Number:

 Enter the document number of the posted invoice you want to modify.

3. Double-Click on Vendor/Customer Line Item:

 In the document overview, double-click on the vendor or customer line item.

4. Change Payment Terms:

 Modify the payment terms field as required.

5. Save the document after making the necessary changes.

 Option B: Using FBL5N/FBL1N (Line-Item Display):

1. Go to Transaction Code: FBL5N (for customers) or FBL1N (for vendors).

2. Enter Vendor/Customer Number:

  Provide the customer or vendor number whose payment terms you want to
change.

3. Select the Line Item:

 Double-click on the specific line item.

4. Click on Change:

 Click the Change button to modify the payment terms as needed.

5. Save the changes once completed.

3. FS00 – Create GL Accounts for Cash Discount

Purpose: Set up the GL accounts for cash discount received (income) and cash discount allowed
(expense).

Steps:

1. Go to Transaction Code: FS00.

2. Create New GL Accounts:

o Cash Discount Received (Income):

 Create a GL account for cash discount received, which will be credited when
cash discounts are taken.

o Cash Discount Allowed (Expense):

 Create a GL account for cash discount allowed, which will be debited when
cash discounts are offered.

3. Save the GL accounts.

4. OBXU – Automatic Account Assignment for Cash Discount Received

Purpose: Configure the automatic account assignment for cash discounts received.

Steps:

1. Go to Transaction Code: OBXU.

2. Assign Chart of Accounts:

o Select the Chart of Accounts used in your system.

3. Enter the Configuration for Cash Discount:

o Provide the GL account number for cash discount received.

4. Save the configuration.

5. OBXI/OBXV – Automatic Account Assignment for Cash Discount Allowed

Purpose: Configure the automatic account assignment for cash discounts allowed.

Steps:
 1. Go to Transaction Code: OBXI (for cash discount received) or OBXV (for cash discount
allowed).

2. Assign Chart of Accounts:

o Select the Chart of Accounts used in your system.

3. Enter the Configuration for Cash Discount:

o Provide the GL account number for cash discount allowed.

4. Save the configuration.

6. Create Payment Terms with Cash Discount

Purpose: Create payment terms that include a cash discount for early payment.

Steps:

1. Go to Transaction Code: OBB8.

2. Create Payment Term:

o Enter a Payment Term ID (e.g., Z02).

o In the Payment Terms Tab:

 Specify the number of days in which the cash discount applies (e.g., 10
days).

 Specify the percentage for the cash discount (e.g., 5%).

o This allows customers to pay a reduced amount if they settle the invoice within the
discount period.

3. Save the payment terms.

7. Create Vendor Master Data with Cash Discount Payment Terms

Purpose: Link the vendor to the newly created payment terms that include cash discounts.

Steps:

1. Go to Transaction Code: XK01 (Create Vendor).

2. Enter Vendor Number:

o Provide a vendor number (e.g., V100).

3. Link Payment Terms:

o In the Payment Terms field, select the payment terms that include the cash
discount.

4. Post Vendor Invoice:

o When posting a vendor invoice, if the exact amount of the discount is unknown,
enter a provisional amount (e.g., 1000).

o Process the open items to check the discount difference.

5. Adjust Amount:
 o After processing the open item, if the discount amount differs, adjust the amount by
double-clicking on the invoice line item.

6. Save the document once the adjustment is made.

8. Payment Terms for Instalment Payments

Purpose: Define Instalment payment terms for splitting payments into multiple parts.

Steps:

1. Create Payment Term Without Days:

o Go to OBB8 and create a payment term without specifying the number of days.

o Activate Instalment Payment in the payment term and save it.

2. Create Instalment Payment Terms:

o 1st Instalment Payment Term: Add the Instalment days and save.

o 2nd Instalment Payment Term: Add the Instalment days and save.

o 3rd Instalment Payment Term: Add the Instalment days and save.

3. Go to Transaction Code: OBB9.

4. Define Terms of Payment for Instalment Payment:

o Click on New Entries and enter the Main Payment Term ID.

o Specify the number of Instalments (e.g., 3 Instalments) and the percentage for each
Instalment.

o Link the created Instalment payment terms.

5. Save the configuration.

9. Create Vendor Master Data with Instalment Payment Terms

Purpose: Link the vendor to the Instalment payment terms.

Steps:

1. Go to Transaction Code: XK01 (Create Vendor).

2. Link Instalment Payment Terms:

o Select the Instalment payment terms created earlier.

3. Post Vendor Invoice:

o Before saving the invoice, click on Simulate to check the Instalment entries.

o The system will automatically split the payment into Instalments.

4. Save the invoice document once confirmed.

10. FBL1N – Display Vendor Line Items

Purpose: Check the due status of vendor invoices.

Steps:

1. Go to Transaction Code: FBL1N.

2. Enter Vendor Number:

o Enter the vendor number (e.g., V100).

3. Enter Period:

o Specify the period to view the invoice status (e.g., January 2024).

4. Display Line Items:

o Review the open and overdue invoices. Instalment payments will show not due until
the due date, and will show as overdue once the Instalment date is passed.

Tax on sales and purchases

1. OBYZ – Check Calculation Procedure / Define Tax Procedure

Purpose: Define the tax calculation procedure, steps, and account keys for input and output taxes.

Steps:

1. Go to Transaction Code: OBYZ.

2. Check Calculation Procedure:

o Click on New Entries to define a new tax procedure.

o Procedure Code: Enter a unique procedure code (e.g., TAX1).

o Description: Enter a description for the procedure (e.g., Sales and Purchase Tax).

3. Control Data:

o Double-click on the Control Data tab and click on New Entries.

o Step Numbers: Define steps for calculation (e.g., Step 100, Step 200, Step 300).

o Calculation Type:

 Enter BASB for the base amount.

 For Input Tax, use MWVS.

 For Output Tax, use MWAS.

o Description: Provide a description for each calculation type (e.g., Base Amount,
Input Tax, Output Tax).

o Account Key:

 For Input Tax, use VST (Input VAT).

 For Output Tax, use MWS (Output VAT).

4. Save the tax procedure.

2. OBBG – Assign Country to Calculation Procedure

Purpose: Assign the calculation procedure to a specific country.

Steps:

1. Go to Transaction Code: OBBG.

2. Assign Calculation Procedure:

o Click on Position and select the country code (e.g., IN for India).

o Enter the calculation procedure code (e.g., TAX1).

o Press Enter to assign the calculation procedure.

3. Save the assignment.

3. FTXP – Define Tax Code for Sales and Purchases

Purpose: Define tax codes for different tax types (e.g., 0%, 10% Input, and Output GST).

Steps:

1. Go to Transaction Code: FTXP.

2. Define Tax Code for 0%:

o Enter the country code (e.g., IN).

o Enter the tax code (e.g., 0%).

o Description: Provide a description (e.g., Zero Tax Rate).

o Tax Type: Select V (for VAT).

o Tax Percentage: Enter 0.

o Deactivate Line: Place the cursor on a blank line and click Deactivate Line.

o Save the tax code.

3. Create 10% Input GST Tax Code:

o Enter tax code (e.g., IGST10).

o Tax Percentage: Enter 10% for input GST.

o Save the tax code.

4. Create 10% Output GST Tax Code:

o Enter tax code (e.g., OGST10).

o Tax Percentage: Enter 10% for output GST.

o Save the tax code.

4. Create GL Accounts (Input/Output GST)

Purpose: Create GL accounts for input and output taxes, including raw materials and sales accounts.

Steps:

1. Go to Transaction Code: FS00.

2. Create Input GST GL Account (Asset Control):

 o Account Type: Select Asset.

o Tax Category: Choose < for input tax.

o Posting without Tax Allowed: Select this option.

o Description: Create a description for the GL account (e.g., Input GST).

o Save the account.

3. Create Output GST GL Account (Liability Control):

o Account Type: Select Liability.

o Tax Category: Choose + for output tax.

o Posting without Tax Allowed: Select this option.

o Description: Create a description for the GL account (e.g., Output GST).

o Save the account.

4. Create Raw Material Account:

o Account Type: Select Expense.

o Tax Conditions: Link to the Input GST GL account.

o Save the account.

5. Create Sales Account:

o Account Type: Select Revenue.

o Tax Conditions: Link to the Output GST GL account.

o Save the account.

5. OB40 – Define Tax Accounts

Purpose: Define tax accounts for automatic posting of tax-related entries.

Steps:

1. Go to Transaction Code: OB40.

2. Assign Tax Accounts:

o Double-click on the VST (Input Tax) or MWS (Output Tax) transaction.

o Select the Chart of Accounts.

o Enter the GL account number for input and output tax (e.g., Input GST GL Account
and Output GST GL Account).

3. Save the tax account assignments.

6. Post Vendor/Customer Invoice Using Single Screen

Purpose: Post invoices for vendors/customers while calculating taxes on the net amount.

Steps:
 1. Go to Transaction Code: FB60 (for Vendor Invoice) or FB70 (for Customer Invoice).

2. Select Editing Option:

o Choose Calculate Taxes on Net Amount.

o Tax Code: Select the appropriate tax code (e.g., IGST10 or OGST10).

3. Enter Invoice Details:

o Fill in the vendor/customer, invoice amount, and other necessary details.

4. Save the invoice once the tax calculation is completed.

7. Post Vendor/Customer Invoice Using Double Screen

Purpose: Post invoices with tax calculation using the double-screen view.

Steps:

1. Go to Transaction Code: F-43 (for Vendor Invoice) or F-22 (for Customer Invoice).

2. Select "Calculate Tax":

o Enter the tax code (e.g., IGST10 for input tax).

o Select Calculate Tax.

3. Post the Invoice:

o After the tax calculation, complete the invoice details and post it.

o Save the document.

8. Monitor Tax Calculation Using FBL1N/FBL5N

Purpose: View the open items and tax postings for vendor and customer invoices.

Steps:

1. Go to Transaction Code: FBL1N (for Vendor Line Items) or FBL5N (for Customer Line Items).

2. Enter Vendor/Customer Number:

o Provide the vendor or customer number.

3. Enter the Period:

o Specify the period for which you want to check the open items.

4. Check the Status:

o The open items will display the tax status, indicating whether the taxes are correctly
calculated and posted.

Withholding tax:

1. Check Withholding Tax Countries

Purpose: Verify which countries have withholding tax settings enabled.

Steps:

1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Financial Accounting (New) → Financial Accounting Global Settings →

Withholding Tax → Extended Withholding Tax → Basic Settings → Check Withholding Tax
Countries.

3. Enter Country Code:

o Input the country code (e.g., IN for India).

o Press Enter to view or configure withholding tax settings for the country.

4. Save the settings if applicable.

2. Define Withholding Tax Keys

Purpose: Define the keys for withholding tax.

Steps:

1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Financial Accounting (New) → Financial Accounting Global Settings →

Withholding Tax → Extended Withholding Tax → Basic Settings → Define Withholding Tax
Keys.

3. Enter Country Code:

o Input the country code (e.g., IN).

o Press Enter.

4. Save the withholding tax keys after configuration.

3. Define Reason for Exemption

Purpose: Configure exemption reasons for withholding tax.

Steps:

1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Financial Accounting (New) → Financial Accounting Global Settings →

Withholding Tax → Extended Withholding Tax → Basic Settings → Define Reason for
Exemption.

3. Enter Country Code:

o Input the country code (e.g., IN).

4. Click on New Entries:

o Exemption Reason Code: Define a code (e.g., EX01).

o Exemption Reason Text: Provide a description (e.g., No Tax Deducted).

5. Save the reason for exemption.

4. Define Withholding Tax Type for Invoice Posting

Purpose: Define the withholding tax type used during invoice posting.

Steps:

1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Financial Accounting (New) → Financial Accounting Global Settings →

Withholding Tax → Extended Withholding Tax → Calculation → Withholding Tax Type →
Withholding Tax Type for Invoice Posting.

3. Enter Country Code:

o Input the country code (e.g., IN).

o Click New Entries.

o Withholding Tax Type: Assign a tax type (e.g., Z1).

o Description: Provide a description (e.g., TDS on Invoices).

o Base Amount: Select Gross Amount as the base amount.

o Rounding Rule: Choose Withholding Tax Common Rounding.

4. Save the withholding tax type for invoice posting.

5. Define Withholding Tax Type for Payment Posting (Advance Amount)

Purpose: Define withholding tax type for payments (e.g., advances).

Steps:

1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Financial Accounting (New) → Financial Accounting Global Settings →

Withholding Tax → Extended Withholding Tax → Calculation → Withholding Tax Type →
Define Withholding Tax Type for Payment Posting.

3. Enter Country Code:

o Input the country code (e.g., IN).

o Click New Entries.

o Withholding Tax Type: Define the tax type (e.g., Z2 for advance payments).

o Description: Provide a description (e.g., TDS on Advance Payments).

o Base Amount: Select Gross Amount as the base amount.

o Rounding Rule: Choose Withholding Tax Common Rounding.

4. Save the withholding tax type for payment posting.

6. Define Withholding Tax Codes

Purpose: Define withholding tax codes used for invoice and payment postings.

Steps:
1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Financial Accounting (New) → Financial Accounting Global Settings →

Withholding Tax → Extended Withholding Tax → Calculation → Withholding Tax Code →
Define Withholding Tax Code.

3. Enter Country Code:

o Input the country code (e.g., IN).

o Click New Entries.

4. Create Tax Code for Invoice Postings:

o Withholding Tax Type: Select Z1 (for invoice-related TDS).

o Tax Code: Assign a code (e.g., Y1).

o Base Amount: Specify the amount on which TDS is calculated.

o Withholding Tax Rate: Enter the TDS percentage (e.g., 10%).

o Posting Indicator: Set to 1 (for standard posting).

o Save the tax code.

5. Create Tax Code for Payment Postings:

o Withholding Tax Type: Select Z2 (for advance payment-related TDS).

o Tax Code: Assign a code (e.g., Y2).

o Base Amount: Specify the amount on which TDS is calculated.

o Withholding Tax Rate: Enter the TDS percentage (e.g., 10%).

o Posting Indicator: Set to 1 (for standard posting).

o Save the tax code.

7. Assign Withholding Tax Types to Company Codes

Purpose: Assign withholding tax types to relevant company codes.

Steps:

1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Financial Accounting (New) → Financial Accounting Global Settings →

Withholding Tax → Extended Withholding Tax → Company Code → Assign Withholding Tax
Types to Company Codes.

3. Click on New Entries:

o Company Code: Enter the company code (e.g., IN01).

o Withholding Tax Type: Select Z1.

o Withholding Tax Agent: Select the withholding tax agent (e.g., vendor, customer).

o Obligated From/To Date: Set the applicable date range for withholding tax.

4. Save the settings.

8. Activate Extended Withholding Tax

Purpose: Activate extended withholding tax settings for the company code.

Steps:

1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Financial Accounting (New) → Financial Accounting Global Settings →

Withholding Tax → Extended Withholding Tax → Company Code → Activate Extended
Withholding Tax.

3. Select Company Code:

o Click Position and choose the company code.

o Activate extended withholding tax for the selected company code.

4. Save the configuration.

9. Automatic Account Assignment for Withholding Tax/TDS Postings

Purpose: Set up GL accounts for withholding tax (TDS) postings.

Steps:

1. Create TDS Payable GL Account:

o Account Type: Liabilities.

o Sort Key: 001.

o F. S. Group: G001.

o Save the account.

2. Create Advertisement Expense Account:

o Account Type: Expenses.

o Sort Key: 001.

o F. S. Group: G001.

o Save the account.

10. OBWW – Define Accounts for Withholding Tax to be Paid Over

Purpose: Assign GL accounts for withholding tax (TDS) postings.

Steps:

1. Go to Transaction Code: OBWW.

2. Define Withholding Tax Accounts:

o Chart of Accounts: Select the relevant chart.

o Debit/Credit: Assign the relevant debit/credit GL accounts for withholding tax.

o Withholding Tax Type: Select Z1 (or relevant withholding tax type).

o Withholding Tax Code: Select Y1 (or relevant tax code).

 o TDS Payable GL Account: Assign this GL account to the debit/credit field.

3. Save the configuration.

11. Withholding Tax Mandatory Settings

A) OMT3E – Activation of Vendor Account Settings

1. Go to Transaction Code: OMT3E.

2. Activate Vendor Settings:

o User Screen Reference: Define a reference name and user ID for the settings.

o Save the configuration.

B) Maintain Company Code Settings

1. Go to Transaction Code: SPRO.

2. Navigate to IMG → Logistics General → Tax in Goods Movements → India → Basic Settings
→ Maintain Company Code Settings.

3. Create New Entries:

4. Define Fiscal Year Settings:

o Enter the fiscal year and the start month (for example, January).

o Click Enter and Save the configuration.

12. XK01 – Create Vendor Master Data with TDS Details

Purpose: Create or update vendor master data to include TDS-related information.

Steps:

1. Go to Transaction Code: XK01.

2. Create Vendor Master:

o Enter the vendor information (e.g., company name, address, etc.).

o In the Tax Information section, navigate to the Withholding Tax tab.

o Enter PAN details (for Indian vendors) and validity dates for the TDS certificate.

o In the Withholding Tax Type field, select the relevant TDS type (e.g., Z1 for invoice
posting).

o In the Withholding Tax Code field, select the appropriate tax code (e.g., Y1).

o Set the Liable checkbox if the vendor is subject to TDS.

3. Save the vendor master data after entering all relevant details.

13. FB60 – Post Vendor Invoice (TDS Calculation)

Purpose: Post a vendor invoice while ensuring TDS is calculated automatically.

Steps:

1. Go to Transaction Code: FB60.

2. Enter Vendor Invoice:

o Select the vendor and enter the invoice details (amount, posting date, etc.).

o Under the Tax Code field, choose the appropriate TDS tax code (e.g., Y1).

o If TDS needs to be applied on a partial amount, adjust the TDS Amount field
accordingly.

o The system will automatically calculate the TDS based on the defined tax code and
the TDS percentage.

3. Manual TDS Adjustment:

o If the vendor has an exemption certificate, you can manually adjust the TDS in the
vendor master data by updating the Withholding Tax tab with the exemption details.

4. Post Invoice:

o Review the details and ensure the TDS is calculated as expected.

o Save the invoice after posting.

14. Manual TDS Posting in FB60 (without Percentage)

Purpose: Post TDS manually if the percentage is not available.

Steps:

1. Go to Transaction Code: FB60.

2. Create Vendor Invoice:

o Select the vendor and enter the invoice amount.

o In the Withholding Tax section, enter the manual TDS amount.

o If the TDS rate is not predefined in the system, manually enter the TDS amount in the
Tax Amount field under the invoice details.

3. Save the invoice after confirming the TDS amount and invoice details.

15. Tax Reporting

Once the withholding tax setup is complete, you can run reports to verify tax calculations and
postings.

Steps:

1. Go to Transaction Code: S_ALR_87012357 (or relevant TDS reports).

2. Run the Report to check:

o The withholding tax amounts for vendor invoices.

o Any discrepancies in TDS calculations or postings.

o Details of tax deductions for each invoice or payment made.

Vendor down payment (advance amount)
1. Create Vendor Down Payment GL in FS00 (Asset)

Purpose: Create a GL account for Vendor Down Payments and link it to the reconciliation account
for accounts payable.

Steps:

1. Go to Transaction Code: FS00.

2. Create GL Account:

o Account Type: Asset (for down payments).

o Chart of Accounts: Enter the appropriate Chart of Accounts (e.g., 1 for the global
chart).

o Account Number: Enter a GL account ID for Vendor Down Payments (e.g., 211000).

o Description: Provide a relevant description, e.g., Vendor Down Payment GL.

o Reconciliation Account: Select Accounts Payable reconciliation account (e.g.,

200000 for Accounts Payable).

o Account Group: Select the appropriate account group (e.g., VEND for Vendor-related
accounts).

3. Save the GL account.

2. OBYR – Define Alternative Reconciliation Account for Down Payments

Purpose: Define the alternative reconciliation account for down payments in the vendor master
data.

Steps:

1. Go to Transaction Code: OBYR.

2. Select Chart of Accounts: Choose the relevant Chart of Accounts.

3. Define Reconciliation Account:

o Special GL Account: Enter the Vendor Down Payment GL account ID in the Special
GL Account field.

o Alternative Reconciliation Account: Link the Accounts Payable GL account (e.g.,

200000) to the Reconciliation Account field.

4. Save the configuration.

3. Create Vendor GL in XK01 for Down Payments

Purpose: Define a vendor with TDS (Tax Deducted at Source) details and assign the appropriate
Reconciliation Account.

Steps:
 1. Go to Transaction Code: XK01.

2. Create Vendor Master:

o Vendor ID: Enter the unique Vendor ID (e.g., 10001).

o Name: Enter the vendor’s name (e.g., Vendor ABC).

o Reconciliation Account: Select the Accounts Payable reconciliation account (e.g.,

200000).

o Tax Information: In the Tax Information tab, enter the TDS details:

 TDS Type: Select the relevant TDS Type (e.g., Z1 for Indian TDS).

 PAN: Provide the vendor's PAN number (e.g., ABCDE1234F for India).

3. Save the vendor master data.

4. F-48 – Post Vendor Down Payment/Advance

Purpose: Record the vendor down payment or advance payment.

Steps:

1. Go to Transaction Code: F-48.

2. Enter Document Details:

o Document Date: Enter the document date (e.g., 01/01/2024).

o Amount: Enter the down payment amount (e.g., 100,000).

o Vendor: Enter the vendor ID (e.g., 10001).

o GL Account: Select the Vendor Down Payment GL account created in FS00 (e.g.,
211000).

o Special GL Indicator: Ensure that the Special GL Indicator is set (e.g., A for down
payments).

3. Post the down payment.

5. FBL1N – Vendor Line-Item Display

Purpose: Display vendor details and special GL transactions.

Steps:

1. Go to Transaction Code: FBL1N.

2. Filter Display:

o Document Type: Choose Normal Items and Special GL transactions.

o Vendor: Enter the vendor ID (e.g., 10001).

o Fiscal Year: Specify the fiscal year (e.g., 2024).

3. Execute to display the line-item details for the vendor.

6. FB60 – Post Vendor Invoice

Purpose: Post an invoice received from the vendor.

Steps:

1. Go to Transaction Code: FB60.

2. Enter Invoice Details:

o Vendor: Enter the vendor ID (e.g., 10001).

o Invoice Amount: Enter the invoice amount (e.g., 150,000).

o Tax Code: Select the relevant tax code (e.g., TDS10 for 10% TDS).

o GL Account: Choose the GL account (e.g., 500000 for expense accounts).

o Invoice Date: Enter the invoice date (e.g., 01/02/2024).

3. Post the invoice.

7. F-54 – Vendor Down Payment Clearing

Purpose: Clear the vendor down payment against the invoice.

Steps:

1. Go to Transaction Code: F-54.

2. Enter Down Payment Clearing:

o Document Type: Choose Down Payment (e.g., DR).

o Vendor: Enter the vendor ID (e.g., 10001).

o Clearing Amount: Enter the clearing amount (e.g., 100,000).

3. Click on "Process Down Payments":

o This option allows the system to automatically clear the down payment amount
against the vendor invoice.

4. Transfer Posting: Double-click on the blue line to make a transfer posting.

5. Add Text: Add a text description for the clearing entry (e.g., "Down payment against
invoice").

6. Save the document after processing.

8. FBL1N – Vendor Line-Item Display (Cleared Items)

Purpose: Verify that the vendor down payment and invoice are cleared.

Steps:

1. Go to Transaction Code: FBL1N.

2. Check Cleared Items:

o Vendor: Enter the vendor ID (e.g., 10001).

o Fiscal Year: Specify the fiscal year.

 o Cleared Items: The cleared items should be visible after processing the down
payment clearing in F-54.

9. F-44 – Manual Clearing of Vendor Items

Purpose: Manually clear open items for the vendor.

Steps:

1. Go to Transaction Code: F-44.

2. Enter Vendor Details:

o Vendor: Enter the vendor ID (e.g., 10001).

o Document Type: Choose Manual Clearing (e.g., SA).

3. Process Open Items:

o Click on Process Open Items to clear any open items.

4. Document Without Values: Select the document without values option for documents
without a direct monetary value, if applicable.

5. Save the clearing document.

TDS with Vendor Down Payment

10. Maintain TDS Details in Vendor Master Data

Purpose: Maintain TDS details in the vendor master for accurate TDS deductions.

Steps:

1. Go to Transaction Code: XK01 (or MK01 for purchasing vendors).

2. Enter Vendor Master Data:

o Vendor ID: Enter the vendor ID.

o Tax Information: Go to the Withholding Tax tab.

o TDS Type: Enter the relevant TDS Type (e.g., Z1 for Indian TDS on invoices).

o PAN: Provide the vendor’s PAN number (e.g., ABCDE1234F).

3. Save the vendor master data.

11. F-48 – Post Vendor Down Payment with TDS

Purpose: Post a vendor down payment including the TDS calculation.

Steps:

1. Go to Transaction Code: F-48.

2. Enter Down Payment:

o Vendor: Enter the vendor ID (e.g., 10001).

o Down Payment Amount: Specify the down payment amount (e.g., 100,000).
 o Tax Code: Ensure that the TDS tax code (e.g., TDS10 for 10% TDS) is selected.

o Special GL Indicator: Set the Special GL indicator to A for down payment.

3. Post the down payment with TDS.

Detailed Notes on GST Configuration and Processes in SAP

1. Pre-requisite Configuration for GST in SAP

Before configuring GST in SAP, ensure the following steps are completed:

1.1 Update SAP System

 Ensure that the SAP system is up-to-date with the latest support packs and patches for GST
configuration. Frequent updates are issued for GST-related requirements.

1.2 Master Data Configuration

 Vendors and Customers: Ensure that vendor and customer master data includes tax-related
fields, such as tax numbers, GSTIN (Goods and Services Tax Identification Number), and tax
classification.

 General Ledger Accounts: Configure GL accounts specifically for GST-related transactions

such as GST Payable, GST Receivable, CGST, SGST, and IGST accounts.

2. GST Configuration in SAP

2.1 Activate GST in SAP

To enable GST in the SAP system, follow the steps below:

1. Go to Transaction Code: SPRO

2. Navigate to:
IMG → Financial Accounting → Financial Accounting Global Settings → Tax on
Sales/Purchases → Basic Settings → Activate GST.

3. Activate GST for India by selecting the checkbox for IN (India).

4. Save the settings.

2.2 Define Tax Codes for GST

Tax codes are essential for applying the correct GST rates during transaction postings.

1. Go to Transaction Code: SPRO

2. Navigate to:
IMG → Financial Accounting → Financial Accounting Global Settings → Tax on
Sales/Purchases → Basic Settings → Check Calculation Procedure.

3. Define Tax Codes for various GST categories such as:

o SGST (State GST): For intra-state transactions.

o CGST (Central GST): For intra-state transactions.

o IGST (Integrated GST): For inter-state transactions.

4. Define Tax Code Examples:

 o GST 5%, GST 12%, GST 18%, GST 28% for different GST rates.

5. Save the tax codes once they are defined.

2.3 Define GST Tax Rates

Define the GST rates corresponding to different tax codes:

1. Go to Transaction Code: SPRO

2. Navigate to:
IMG → Financial Accounting → Financial Accounting Global Settings → Tax on
Sales/Purchases → Calculation → Define Tax Rates.

3. Define the rates for:

o CGST and SGST (for intra-state).

o IGST (for inter-state).

4. For each tax code (e.g., 5%, 12%, 18%, etc.), assign the appropriate rate.

5. Save the tax rates.

2.4 Define GL Accounts for GST

Create GL accounts for GST-related transactions:

1. Go to Transaction Code: FS00

2. Create the following GL accounts:

o GST Payable: For the liability related to GST.

o GST Receivable: For GST that is receivable from the government.

o CGST, SGST, IGST Accounts: Specific accounts to record CGST, SGST, and IGST
transactions.

3. Assign these accounts to tax codes so that they are used automatically during GST postings.

3. GST Transaction Process Flow in SAP

3.1 GST in Purchase Transactions (Vendor)

1. Create Purchase Order (ME21N):

o In the purchase order, select the appropriate tax code (e.g., CGST, SGST, IGST).

o SAP will automatically apply the tax codes based on the vendor's location (intra-state
or inter-state).

2. Post Vendor Invoice (MIRO):

o In the vendor invoice, SAP calculates the GST (CGST, SGST, or IGST) based on the
defined tax codes.

o Accounting Entries:

 Debit: Vendor Invoice Account (Expense/Asset account)

 Credit: GST Payable Account (CGST, SGST, or IGST)

 Credit: Accounts Payable (Vendor Account)

3.2 GST in Sales Transactions (Customer)

1. Create Sales Order (VA01):

o During the creation of a sales order, SAP automatically determines the tax codes
based on the customer and delivery location.

o The system applies tax codes such as CGST, SGST, or IGST based on the state of the
customer (intra-state or inter-state).

2. Post Customer Invoice (VF01):

o When posting the invoice to the customer, SAP calculates the GST based on the
configured tax codes.

o Accounting Entries:

 Debit: Accounts Receivable (Customer Account)

 Credit: Sales Revenue (Revenue Account)

 Credit: GST Receivable (CGST, SGST, or IGST)

3.3 GST on Payment Transactions

1. Vendor Payment (F-53):

o When processing a payment to the vendor, SAP clears the GST payable account along
with the vendor account.

2. Customer Payment (F-28):

o For customer payments, SAP clears the GST receivable account along with the
customer account.

4. GST Reporting in SAP

SAP provides multiple reports to ensure compliance with GST regulations. These reports can be
generated based on the data entered the system.

4.1 GST Return Reports

1. GSTR-1 (Outward Supplies):

o Use transaction J1IG to generate the GSTR-1 report, which provides details on
outward supplies, GST collected, and taxable value.

2. GSTR-2 (Inward Supplies):

o The GSTR-2 report provides details on inward supplies and input tax credit.

o Use J1IG to generate the GSTR-2 report as well.

3. GSTR-3B (Summary of Returns):

o This is a summary return for tax payments.

o Use J1IG to generate this report.

4.2 GST Payment Register

The GST Payment Register tracks the payments of GST to the government.

 Transaction Code: F-53 to make GST payments.

  Use this code to process payments for CGST, SGST, and IGST based on the tax amounts
calculated by the system.

4.3 GST Reconciliation Report

Reconciliation between the SAP system and the data filed with the GSTN portal can be performed
through reconciliation tools in SAP. Discrepancies can be identified and corrected before submission.

5. GST Accounting Entries in SAP

5.1 Vendor Transactions (Purchases)

Example: If a purchase invoice is for ₹10,000 with 18% GST:

 Total Invoice Amount: ₹10,000

 GST (CGST + SGST or IGST): ₹1,800 (₹900 CGST and ₹900 SGST)

Accounting Entries:

 Debit: Purchase Account (₹10,000)

 Debit: GST Receivable (₹900 CGST)

 Debit: GST Receivable (₹900 SGST)

 Credit: Vendor Account (₹12,800)

5.2 Customer Transactions (Sales)

Example: If a sales invoice is for ₹10,000 with 18% GST:

 Total Sales Amount: ₹10,000

 GST (CGST + SGST or IGST): ₹1,800 (₹900 CGST and ₹900 SGST)

Accounting Entries:

 Debit: Accounts Receivable (₹12,800)

 Credit: Sales Revenue (₹10,000)

 Credit: GST Payable (₹900 CGST)

 Credit: GST Payable (₹900 SGST)

6. Manual GST Clearing

In cases of discrepancies or adjustments, you can use manual clearing to reconcile GST accounts:

1. Transaction Code: F-03

o This transaction allows you to clear GST Payable and GST Receivable accounts
manually.

o Ensure that the entries match with the tax reports to clear the accounts accurately.

7. GST Filing and Compliance

1. GSTR-1 Filing:
 o Submit details of outward supplies, including GST collected, through the GSTR-1
return.

2. GSTR-2 Filing:

o Submit details of inward supplies and input tax credits through the GSTR-2 return.

3. GSTR-3B Filing:

o Submit the summary of tax liability and input tax credit.

MM60- CHECK MATERIAL LIST

ME23N- DISPLY PURCHASE ORDER

MMPV- MM POSTIING PERIODS

MMBE- CHECK THE QUANTITY

SE16N->BSET- SEE THE BASE AND TAX AMOUNT