Hello All,

I was facing an issue regarding the necessity to edit the reconciliation account derived from the customer/vendor data without using a SGL indicator.

Many SCN discussion confirm that it’s not possible as in standard the GL account is derived from the customer/vendor master data, nevertheless, there is a “standard” way (no specific development) to edit and select the reconciliation account we need during posting  and without using the SGL indicator:

Here is the steps :

1. First, specify your GL accounts that you want to choose from, for example let say Recon. Accounts
   • 41110010 (entered in customer master data)
   • 41110011
   • 41110012

  2. check the box on  GL account masetr data  (Create/bank/interest TAB)  “Reconcil.acct ready for input” (Tcode FS00)

3 . If this option is not visible, change your Field status group of your Account group (Tcode OBD4) in “Document entry”

4. Go to transaction S_ALR_87002480 to customize your entries :

For each GL account that will be derived form the customer master data, enter the possible entries you need

That’s All 

Now when your are posting with FB01 or FB70 for customers invoices, you will have the possibility to change the reconciliation account, the field is editable

but only accept the GL account entered in the table above (step 4).

My posting can look like :

And GL view :

Voila !

I hope it helps

Tamim

Introduction

The withholding tax for vendor and customer should follow the Nota Fiscal items to have the AP/AR line item deducted.

The Brazilian Nota Fiscal is posted automatically by MIRO transaction code for vendor and by VF01 for customer and both have their specific calculation procedures defined in J1BTAX transaction. Usually a nota fiscal (for vendor and customers) has many items (service, material and subcontracting), and some items can have the withholding tax and others no at the same invoice or billing.

The customizing done only in FI will apply the Withholding Tax considering the AP/AR line item total amount generating a mismatch between the Withholding done in FI document with Brazilian Nota Fiscal.

This document describes the relevant configuration to connect the withholding tax type and code to the Nota Fiscal condition type to receive the amount defined in the Nota Fiscal having the accounting document posted with the same amount defined in the nota fiscal calculation procedure.

Basic settings for extended withholding tax

All configurations will be done following the SPRO -> IMG -> Financial Accounting (New) -> Withholding Tax -> Extended Withholding Tax.

The basic settings to start the definition of withholding tax configurations are the definitions done in Type level and Code level. Let´s understand the important configuration done in both of them.

The WHT Type and Code are defined by Country Code and it will be applied for the companies assigned to that country. The G/L account can be setup differently in company code level as well the assignment of withholding tax type to it.

Follow the draw bellow to understand the assignments:

This document will focus on the calculation, Withholding tax Type and Code setup to link them to the MM and SD condition type.

Setting up the withholding tax type

The initial setup is the definition of withholding tax type that will be the same for Invoice and Payment Post.

The tax amount will be informed by Nota Fiscal to FI accounting, so the Base Amount must be defined as Modified tax amount, this means that those transactions that you specified in Customizing for the withholding tax base amount are used as the tax base:

This setup will required the assignment of WHT Type to a processing key IMG -> Withholding Tax -> Extended Withholding Tax -> Calculation -> Withholding Tax Base Amount -> Define Processing Key for Modified Tax Amount

The process key defined at this moment is the account key used in the Calculation Procedure condition type.

Setting up the withholding tax code

There is two ways to go from here, receive the Base Amount and apply the WHT rate to have the amount or receive the tax amount already calculated by nota fiscal.

The first option can generate rounding difference since the WHT amount is calculated by Nota Fiscal Item number while the FI posting is calculated on the AP or AR amount.

The second option will generate the FI accounting withholding tax posting with the same amount as the Nota Fiscal, but the rate will be always set as 100%.

IMG -> Withholding Tax -> Extended Withholding Tax -> Calculation -> Withholding Tax Code -> Define Withholding Tax Codes

The example below will link the Withholding Tax Type and Code “CO” with the Tax Amount condition in TAXBRA calculation procedure, so the rate will be defined as 100% since the accounting document will receive the calculated amount to be posted:

In this document, I have tried to present an example to understand Realized Foreign Exchange Gain/Loss and related postings in SAP in simple terms. Please note that Forex Revaluation which is a Month End Process is a slightly different concept than presented here. The concept below works when we clear Customer/Vendor/G/L line items which results in Actual Foreign Exchange Gain/Loss.

Configuration in OB22 for Parallel Currencies

As per the settings above

• Translation to Local Currency is as per Translation Date and taking Transaction currency as basis
• Translation to Group Currency is as per Translation Date and taking First Local currency as basis

Customer Document Posted

Customer Document Clearing Posted

A difference of 0.30 CAD (Local Currency) was debited as Forex Loss and 1.56 USD (Group Currency/Local Currency2) was credited as Forex Gain

To understand the posting, we need to look at the OB09 settings of the Recon Account for the customer, OB08 rates on the Customer document posting date and Clearing document posting date and calculate the Realized Gain/Loss

Recon Account of the Customer: 11000

Forex Gain/Loss calculation in Local Currency

--------------------------------------------------------------

Document Currency = CNY

Local Currency = CAD

Exchange rate type ‘M’ is to be used for translation as per OB22 settings and the Translation is to happen from Transaction Currency

USD is the intermediary currency for exchange rate type ‘M’. So, translation from CNY to CAD will be calculated using CNY-USD and CAD-USD exchange rates from OB08 as on the Customer document posting date and Clearing document posting date

Customer Document Posting Date : 10^th Feb 2016

Clearing Document Posting Date : 20^th Feb 2016

OB08 Rates

Customer Document Clearing Posted

Customer Line item Amount in CAD (from Customer Document Posted)

=Amount in CNY * (CNY-USD rate as on 02/10/2016) / (CAD-USD rate as on 02/10/2016)

= 1250 CNY * 0.15209 / 0.71929

= 264.31

Clearing Line item Amount in CAD (from Clearing Document Posted)

=Amount in CNY * (CNY-USD rate as on 02/20/2016) / (CAD-USD rate as on 02/20/2016)

= 1250 CNY * 0.15335 / 0.72605

= 264.01

Hence, Forex Loss in Local Currency = 264.01-264.31 = 0.30 CAD posted to Account 81160 as per the setting below.

OB09 settings for Currency Type 10 (Local Currency) and Recon Account 11000

Forex Gain/Loss calculation in Group Currency (Local Currency2)

------------------------------------------------------------------------------------------

Document Currency = CNY

Local Currency = CAD

Group Currency (Local Currency2) = USD

Exchange rate type ‘M’ is to be used for translation as per OB22 settings and the Translation is to happen from Local Currency

USD is the intermediary currency for exchange rate type ‘M’. So, translation from CAD to USD will be calculated using CAD-USD exchange rate from OB08 as on the Customer document posting date and Clearing document posting date

Customer Document Posting Date : 10^th Feb 2016

Clearing Document Posting Date : 20^th Feb 2016

OB08 Rates

Customer Document Clearing Posted

Customer Line item Amount in USD (from Customer Document Posted)

=Amount in CAD * (CAD-USD rate as on 02/10/2016)

= 264.31 CAD * 0.71929

= 190.12

Clearing Line item Amount in USD (from Clearing Document Posted)

=Amount in CAD * (CAD-USD rate as on 02/20/2016)

= 246.01 CAD * 0.72605

= 191.68

Hence, Forex Gain in Group Currency (Local Currency2) = 191.68 – 190.12 = 1.56 USD posted to Account 81160 as per the setting below.

OB09 settings for Currency Type 30 (Group Currency) and Recon Account 11000

Please note that the document shows Classical G/L screenshots, but, the concept of Forex calculation is still the same.

When we use the Foreign Currency Valuation Run in the month end close process, the exchange loss/gain posted is Unrealized and is reversed at the beginning of the next month. Actual Realized Gain/Loss is when we clear the open items on receipt/sending payment.

Configuration in OB22 for Parallel Currencies

As per the settings above

• Translation to Local Currency is as per Translation Date and taking Transaction currency as basis
• Translation to Group Currency is as per Translation Date and taking First Local currency as basis

Documents to be Valuated

2 of the Customer Documents Posted are as below. We will look into the Unrealized Forex Gain/Loss calculations for these documents.

Note that on the Document Posting date, Exchange Rate type ‘M’ would be used

OB08 Rates

Amount in Transaction Currency = Amount in Group Currency (LC2) = 1050 USD

Amount in Local Currency (CAD)

= Amount in USD / (CAD-USD rate on 02/10/2016)

= 1050/0.71929

= 1459.77

OB08 Rates

Amount in Transaction Currency = 1350 GBP

Amount in Local Currency (CAD)

= Amount in GBP * (GBP-USD rate on 02/10/2016) / (CAD-USD rate on 02/10/2016)

= 1350*1.44344/0.71929

= 2709.12

Amount in Group Currency /LC2 (USD)

= Amount in GBP * (GBP-USD rate on 02/10/2016)

= 1350*1.44344

= 1948.64

Valuation Method Set up

Foreign Currency Valuation for Balance Sheet Accounts (We are using customer documents and hence, the Recon account would fall under this category) is generally done using Month End Exchange Rate. So, first, a Valuation Method is set up to be used with the Foreign Exchange Valuation Run (In our case, 1001 is the Month End Rate)

1001 has USD defined as Reference currency. Hence, all valuations would be with reference to USD (i.e. USD would be the intermediary currency)

Recon Account

Recon Account of the Customer: 11000

Valuation Run to Local Currency (Currency Type = 10)

As per OB22 settings the Translation is to happen from Transaction Currency to Local Currency

We are running for Feb Month End with the Valuation Method created “ZBAL” and Currency Type = 10 (CAD)

OB08 Rates

Exchange Rate type ‘1001’ would be used as set up in Valuation Method ZBAL for Month End

Exchange Rate Type ‘M’ would be used on Document Posting Date

USD to CAD on Document Posting Date

=1/(CAD-USD rate on 02/10/2016) = 1/0.71929 = 1.39026

USD to CAD on Month End

=1/(CAD-USD rate on 02/29/2016) = 1/0.7388 = 1.35355

Difference for document 6000000030

= Amount in USD * (USD to CAD on Month End - USD to CAD on Document Posting Date)

=1050 * (1.35355 – 1.39026) = -38.55

GBP to CAD on Document Posting Date

= (GBP-USD rate on 02/10/2016) / (CAD-USD rate on 02/10/2016) = 1.44344/0.71929 = 2.00676

GBP to CAD on Month End

= ( GBP-USD rate on 02/10/2016) / (CAD-USD rate on 02/29/2016) = 1.39519/0.7388 = 1.88845

Difference for document 6000000033

= Amount in GBP * (GBP to CAD on Month End - GBP to CAD on Document Posting Date)

=1350 * (1.88845 – 2.00676) = -159.71

The Account Determination for posting Unrealized Gain/Loss for Currency Type = 10

Below is the posting from Foreign Currency Valuation Run. Since the difference is negative and the document is customer document, it is a loss.

Posting Date = 02/29/2016

Reversal is also posted by the Foreign Currency Valuation Run.

Posting Date = 03/01/2016

Valuation Run to Local Currency (Currency Type = 30)

We are running for Feb Month End with the Valuation Method created “ZBAL” and Currency Type = 30 (USD)

OB08 Rates

Exchange Rate type ‘1001’ would be used as set up in Valuation Method ZBAL for Month End. As seen above, applicable Month End Rate is 0.7338

Exchange Rate Type ‘M’ would be used on Document Posting Date. As seen above, applicable rate is 0.71929

Difference for document 6000000030

= Amount in CAD * (CAD-USD on Month End – CAD-USD on Document Posting Date)

=1459.77 * (0.7388 – 0.71929) = 28.48

Difference for document 6000000033

= Amount in CAD * (CAD-USD on Month End – CAD-USD on Document Posting Date)

=2790.12 * (0.7388 – 0.71929) = 52.86

The Account Determination for posting Unrealized Gain/Loss for Currency Type = 30

Below is the posting from Foreign Currency Valuation Run. Since the difference is positive and the document is customer document, it is a gain.

Posting Date = 02/29/2016

Reversal is also posted by the Foreign Currency Valuation Run.

Posting Date = 03/01/2016

Link to understanding Realized Gain/Loss --> Simple Example for understanding Realized Forex Gain/Loss

Introduction

Translation process in SAP converts amount posted in Local Currency (also known as Company Code Currency) into Group Currency for the purpose of Group Reporting. Translation Sets contain the GL accounts on which posting can happen and therefore would be considered for currency translation.

This document reveals the process to create translation sets in SAP. Newly created sets must be assigned to the correct active Translation Methods.

Configuration

Configuration of Translations Sets & Methods involves the following steps:

• Creation of Translation Sets
• Creation of Translation Methods
• Adding Sets to Translation Methods
• Validating Assigned Sets to Translation Methods

Creation of Translation Sets

  Enter Transaction code: GS01

1. Enter Set ID (as per the request):A_OPACC_9988110_OPEN
2. Enter Table e.g. XXREPO
3. Select Set type: Basic Set
4. Enter
5. Enter Field name RACCT (Account Number)
6. Enter a Description e.g. 9988110_OPENING RATE
7. Enter Accounts to be included in the set (as per the request).
8. Select Save

This process needs to be repeated until all the new sets have been created.

For example: Below mentioned 3 sets have been created-

• Set name: A_OPACC_9988110_OPEN

• Set name: A_OPACC_9988220_CLOSE

• Set name: A_OPACC_9988330_AVERAGE

Creation of Translation Method

1. Enter Transaction code:- GCW4
2. Translation method– AAA01 (for example)
3. Name of Translation Method– Dummy Method 1 (for example)
4. Enter Table Name – AAREPO (for example)
5. Enter Usage Indicator *– 2 (for example)

*Usage Indicator: currency translation usage FI-GL/-LC - The entry indicates whether to use the currency translation method from the special ledger or from the consolidation system.

This is how below Translation Methods have been created:

• AAA01Dummy Translation Method for Operational GL A/C's)
• GGG01 (Dummy Translation Method for Group GL A/C's)

Adding Sets to Translation method

All sets must be added to either AAA01 or GGG01 Translation Methods, depending on whether GL account in sets is Operational GL account or group GL account.

Steps for Adding New Sets to Translation Methods

1. Enter Transaction code: GCW4
2. Double click on the Translation Method required e.g. AAA01     

3. Within the method find the most logical place to insert the set (take a note of the number)
4. Select Create 

5. Ensure Translation entry radio button is selected
6. Enter Insert after field the number that was noted above, the new set will be added after that entry.

• FS Item Set: Enter New Set Name (Set name) e.g.A_OPACC_9988110_OPEN
• Exchange rate indicator: enter From Template
• Translation Key: enter From Template
• Debit Item: enter From Template (Account got difference postings column)
• Credit Item: enter From Template (Account got difference postings column)
• Select Save

Based on the set names to be created, the following information is required before commencing the build:

• Translation Method
• Table
• Exchange Rate Indicator
• Translation Key

Translation Methods

The labeling of the new sets is based on whether the set includes Operational GL Accounts or Group GL Accounts. These sets are assigned to Translation Methods: AAA01 or GGG01 accordingly.

Table

Each set must be assigned to a table. This is because sets are table specific and the tables to be used are the summary or the totals tables when creating new sets.

• Operational Accounts: AAREPO (for example)
• Group Accounts: GGREPO (for example)

Exchange Rate Indicator

This is determined by the naming convention of the set.

• Opening
• Average
• Closing

Translation Key

This is determined by the naming convention of the set.

• Opening
• Average
• Closing

For example -

For creating FS item set: A_OPACC_9988110_OPEN (OPENING RATE)

     For creating FS item set: A_OPACC_9988220_CLOSING (CLOSING RATE)

For creating FS item set: A_OPACC_9988330_ AVERAGE (AVERAGE RATE)

This process needs to be repeated for each newly created translation set

Once all the sets have been added to the translation method e.g. AAA01, the method needs to be validated.

Validating Sets Assigned to Translation Methods

Following steps needs to be followed for validating translation method to which new sets have been assigned.

• '-' in Check column (Blank): This means that the method has not yet been checked
• Select the check button now

• Once the check has been completed, the Check column will have one of the following statuses:

'E': The method was checked with errors

'X': The method was checked without errors

If the method has an ‘E’ in the column, then there are errors in that translation method. This could be due to overlapping accounts in assigned sets. The sets in question will be displayed in Validation Report and further investigation needs to be done to correct the errors.

Example of Validation Error Report for Translation Method AAA01 –

Following error has occurred due to presence of same GL account in both the sets at line number 100 & 120 in Translation Method AAA01.

To correct this error, change/ delete the GL account from any one of these two sets.

• Once the corrections have been made, the translation method needs to be validated again and the field will be populated with ‘X’ in the Check column.
• If the method has ‘X’ in the column, then this can be flagged as Active

     Once all the sets have been assigned to the required methods and these methods are activated, the build is complete.   

Testing

As a part of testing, following checks need to be made:

Check 1: Sets Created

1. Transaction code SE16
2. Table: SETLEAF

3. Enter
4. Select Multiple Selection button against Set ID field, Enter the New Sets created in the Single Values tab and Execute

Check 2: FS Item Sets Created

1. Transaction code: SE16
2. Table: T884

3. Enter
4. Select Multiple Selection button against FS item set 1 field, Enter the New Sets created (from the Template) in the Single Values tab and execute

Check 3: Journal Posting

1. Transaction code: FB50
2. Post a journal using Accounts that have been included in the newly created Translation Sets

Check 4: Executing the Translation Program

1. Transaction code: SA38
2. Run program: RGUUMR01 (FI-SL Currency Translation Program)
3. Check if Period & Year have been updated
4. Execute (preferably in Background)

Hello Everyone,

In this series, I would like to present a bunch of quick 20 Tips related to FI/CO/AA that may come handy to you. I cant claim you will find all of them to be new, but there will be something for everyone, to a great extent

Hope you enjoyed reading this. Expect more in the upcoming series

Your actions:

1) Share with your colleagues and within your teams

2) Leave your Feedback / Comments after reading the document. (You can choose not to, but it makes me happy if you do so )

Regards

Ajay Maheshwari

Prerequisite: A working knowledge in OpenText VIM

Introduction: A document in VIM (DP document) can be created using one of the following ways:

1. OCR: Invoices are scanned and read using OCR. The values from the scanned invoices are filled in the DP document.
2. Electronic documents like pdf or XML: Invoices are created by reading and passing the values from electronic document to DP document
3. Manually creating the document: Documents are manually created using either OAWD or /n/opt/vim_7ax1. The invoices are manually attached.

In either of the cases, a copy of the invoice (scanned image or pdf) is attached to the DP document. These invoices are stored in Content Repository Server or Archive Server. ArchiveLink is responsible for interactive between Archive Server and VIM and/or SAP. ArchiveLink document type is assigned to a workflow when the document associated with it is uploaded.

Early Archiving: It is the process where documents scanned are archived before the details extracted from them are entered into the system. Following configuration needs to be done for it:

          1. Create Content Repository ID: In order to archive the scanned images we need to first create the Content Repository ID. Below are the steps:

                         a. Create content repository by executing transaction OAC0 and click on create button

                         b. Enter the details as per your system requirements. Document Area will be ArchiveLink.

          2. Create Presetting Folder: Documents can be stored using OAWD. If the related documents are grouped then it gives more effective way to manage and create documents. A presetting folder represents a preset group of document types. They can be related by workplace or by an application. For each group, we can determine the agents responsible for its corresponding work item.

                         a. Go to T-Code OAWS and click on the "New Entries" button

                         b. Give the Presetting Folder Name (Pr) and Description (Long Text) and save it.

                         c. Goto OAWS and for the Presetting folder (created in above step) go to the subfolder "Entries" by selecting the Pr and double clicking on "Entries". Click on "New Entries" button.

                         d. Select the document type for the presetting folder and select the applicable storing type. (NOTE: Object type (OT) and Agent ID are optional). There are four storing types:

1. Storing for subsequent entry
2. Storing for subsequent assignment
3. Store and enter
4. Store and assign

          3. Create ICC Archive Document Type: This is required to be created so that every incoming invoice with a given document type is stored in predefined archive storage and a customized workflow is triggered for each of the document types.

                         a. Execute T-Code OAD5. This calls the ArchiveLink document type customizing wizard. Click on continue button

                         b. Provide document type and Description. Click on continue button.

                         c. Note that workflow document type option is selected. Click on Continue button

                         d. Provide details of Object Type, Method, Task, and Assignment. Click on Continue button.

                         e. Click continue and go to Storage system.

                         f. Provide Content Repository ID and Link. Click on Continue button.

                         g. Select the presetting folder that we have created and click on continue button. It is here where ICC and Presetting folder are linked. Now based on the document type in the presetting folder the system will pick the content repository from the setting done in the previous step. Skip the "Create New Presetting" as we have already created require the Presetting folders.

                         h. Select the same storage option done for presetting folder in step 2.d. Click on continue button.

                         i. Click on the "Complete" button to save the changes.

          4. Link Archive Document Type to VIM object: This configuration needs to be done in order to know where to store the incoming invoices.

                         a. Go to T-Code OAC3 and click on New Entry button

                         b. Provide details as used in Step 3 and save the changes

          5. Link Archive Document Type to SAP object: This configuration needs to be done in order to know how to link the posted or parked documents in SAP with that of VIM.

                         a. Go to T-Code OAC3 and click on New Entry button. Provide the below entries and save.

With this, we complete the ArchiveLink configuration. Now, we know where the documents are stored and saved. Hope you find it useful.

Roles in VIM is different from SAP workflow roles. Role in VIM is used to classify the users based on the business activity they are involved in.  In VIM roles are based on the product code. VIM offers following product codes:

1. 005: Product code for Document Processing (DP) based activities
2. LIX: Product code for Logistic Invoice Verification (LIV) process (PO parking or PO blocking)
3. PIR: Product code for Non Purchase-Order parking workflow

Below are the scenarios for the better understanding of the relationship between roles and product codes.

Scenario 1: The document should get blocked if there is price discrepancy for PO based DP document. The document should go to Account Payables Processor (Role will be AP_PROC) to review and approve the price discrepancy. Which product code will be used in this scenario?

Solution: Role AP_PROC will be created against product code LIX as LIX is for PO blocking.

Scenario 2: If there are any issues with DP document where it violates any business rule (say currency mismatch) then the document should go to Account Payables Processor (Role will be AP_PROC) for further processing. Which product code will be used in this scenario?

Solution: Role AP_PROC will be created against product code 005 as 005 is for DP processing.

Following steps are involved in role creation:

Define Roles: Roles can be defined by using T-Code /n/OPT/CP_9CX5 and by providing following inputs:

1. Product Code: 005 or LIX or PIR
2. Role: It is the responsible party or role that we want to create.
3. Description: It is the description of the role.
4. Function Module: If any FM is applicable
5. Key Determination: Uncheck it if the role will be based on organization data such as Company Code, Plant etc.
6. Object Type

FM, Key Determination, and Object Type are used based on the template. Please refer Role Template for more details on them.

Define Role Templates: Template helps to determine the role applicable in a workflow. Roles can be Static, Semi-Dynamic or Dynamic. If the role is determined only on the basis of certain parameters like Company Code or Plant then the template is Static. If it is determined based on a certain structure like Organization Hierarchy then it is Semi-Dynamic and if it is determined based on function module then it is Dynamic. Role template can be maintained by using T-Code /n/OPT/CP_9CX2.

Following parameters are provided:

1. Template ID: ID of the template that you wish to create
2. Description: Description of the template
3. Type (Static, Semi-Dynamic or Dynamic). Based on the type we select Key Determination (for Static), Org Unit (for Semi-Dynamic) and FM (for Dynamic).
4. Allow Org:
5. Agent Type
6. Agent ID
7. Function Module

Template fields are then maintained so that system can determine the role based in runtime on the fields mentioned in the template. Following parameters are provided: 

1. Field ID: Fields that will be used to determine the role
2. Ref. Table: Table which will be referred for fetching the field
3. Ref. Field: Technical name of the field in the Ref. Table
   
4. Search Help
5. Allow Range
6. Wild Card

Since templates can be reused for different product codes or roles hence template field details are maintained by providing product code, object type, and Attribute. 

Assign Templates to Role: We have now defined roles and templates. We now have to assign templates to the role so that the role can be determined based on the template which is assigned to it. A role can be assigned with more than one template however at a time only one template can be active. This can be done by using T-Code /n/OPT/CP_9CX2 and maintaining values for following:

1. Product Code: Either 005, LIX or PIR
2. Responsible Party: These are the roles what we have defined.
3. Key Determination: Template ID
4. Active: Checking this box will make the template ID active.

Maintain Role Determination Settings: We have now mapped roles and template but we still need to define the values that will be used in runtime for role determination. This is carried out by using transaction /n /OPT/CP_9CX4. For each role under a product code, we need to maintain the values of the fields or Org unit or FM (depending upon if they are Static, Semi-Dynamic or Dynamic type) which are defined in the template.

Maintain Chart of Authority (CoA): I have given a brief explanation on CoA in my previous document (please refer: http://scn.sap.com/docs/DOC-57917). In version 7 invoice approver can be determined based on two logics:

1. Simple approval: It is same as the old version i.e. gross amount and manager's information.
2. Level based approval: Approvers are determined based on levels and packs. Levels are defined for approval limits i.e. each level will have different amount range that can be approved by that level. For example: We can have different set of approvers for amount ranges: $0 - $5000, $5000 - $10,000, $10,000 - $20,000 and so forth. Also, they can be further divided based on cost center. For example: for the amount range level of $10,000 to $20,000 we can have different approvers for different cost centers.

NOTE: 

1. CoA is used for Non-PO scenarios. For PO scenarios, CoA is not used. The approver (first and only) in PO scenario is determined based on baseline implementation.
2. CoA can be configured to include complexities like approvers can be determined based on amount limit, company code, cost center etc.
3. One can only define the user details in CoA and use a custom logic to determine the approver. In such a scenario all the approvers should be maintained as users in CoA and other tabs in CoA (Coder and CoA details) can be left empty.

Prerequisite: Cost objects are maintained for view /OPT/BL_T401V and fields for view /OPT/BL_T402V

T-code to access old CoA is /n/OPT/VIM_7CX1 and to access new CoA is /n/OPT/VIM_APPR_COA. In new CoA, there is a tab for approval limit. In this tab, we can maintain level based approval configuration.

Above screen shot is of the old CoA. T-code /n/OPT/VIM_7CX1

Above screen shot is of the new CoA. T-Code /n/OPT/VIM_APPR_COA

Substitute setup: VIM allows setting up of substitute for other users by executing T-Code /n/ORS/MAIN_SUBS

I hope this document will be useful for basic understanding and working of roles in OpenText VIM

In this document, we are going to discuss Rollout Criteria that will trigger parking (for PO and Non-PO) and blocking (for PO) of documents and setting up of Event Linkages for them.

Rollout Criteria : In VIM one might want to have a parking process (Blocking process only for PO) defined on the basis of a specific combination of Company Code, Document Type and Plant (NOTE: In the case of Non-PO plant will not be the criteria). Rollout Criteria helps us to define these. We can also say that they are the workflow start conditions. When rollout criteria are defined then following tables are impacted:

Company Codes: /OPT/VIM_CCODE_A

Document Types: /OPT/VIM_DTYPE_A

Plants: /OPT/VIM_PLANT_A

Event Linkages: In the Rollout Criteria we have defined the parameters against which Parking or Blocking process will be triggered but event linkages are where we set up the FMs and only after activating it we are able to trigger the process.

PO Parking Process

Define Rollout Criteria: In order to define the rollout criteria go to the path: Vendor Invoice Management > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Rollout Criteria > Allowed Company Codes, Plants, Document Types.

1. Allowed company codes: Company codes can be allowed for both PO and Non-PO document types. Click on "New Entry" button in order to add a new company code

2. Allowed Plants and Document Types: Select the company code and then double click on "Allowed Plants" and/or "Allowed Document Type" folder on the navigation panel on the left. Maintain the entry as required.

Receiver function module (in event linkages) triggers the workflow is triggered based on the data maintained in this setting. 

Define Event Linkages:

1. Go to T-Code /n/OPT/VIM_IMG241 (Path: Vendor Invoice Management > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Rollout Criteria > Event Linkages (PO Parked Invoices)). Maintain the FM

2. Check the "Linkage Activated" checkbox to ensure that event linkage triggers the PO parking Process.

PO Blocking Process

Define Rollout Criteria: Just like PO parking we can set up criteria for PO blocking. Go to the following path: Vendor Invoice Management > PO Based Invoice Configuration > Blocked Process Configuration > Rollout Criteria > Allowed Company Codes, Plants, Document Types.

1. Allowed company codes: Click on "New Entry" button in order to add a new company code

2. Allowed Plants and Document Types: Select the company code and then double click on "Allowed Plants" and/or "Allowed Document Type" folder on the navigation panel on the left. Maintain the entry as required.

Receiver function module (in event linkages) triggers the workflow is triggered based on the data maintained in this setting. 

Define Event Linkages:

1. Go to T-Code /n/OPT/VIM_IMG311 (Path: Vendor Invoice Management > PO Based Invoice Configuration > Blocked Process Configuration > Rollout Criteria > Event Linkages for Process (PO Blocked Invoices)). Maintain the FM

2. Check the "Linkage Activated" checkbox to ensure that event linkage triggers the PO parking Process

Non-PO Parking Process

Define Rollout Criteria: Just like PO we can define the criteria for Non-PO parking process. NOTE: In Non-PO process we will not have plants as the criteria. Go to the following path: Vendor Invoice Management > Non-PO Based Invoice Configuration > Parked Invoice Processing Configuration > Rollout Criteria > Allowed Company Codes, Plants, Document Types.

1. Allowed Company Codes: Company codes can be allowed for both PO and Non-PO document types. Click on "New Entry" button in order to add a new company code

2. Allowed Document Types: Select the company code and then double click on "Allowed Document Type" folder on the navigation panel on the left. Maintain the entry as required. NOTE: Plants cannot be maintained for Non-PO document type.

Receiver function module (in event linkages) triggers the workflow is triggered based on the data maintained in this setting. 

Define Event Linkages:

1. Go to T-Code /n/OPT/VIM_IMG239 (Path: Vendor Invoice Management > Non-PO Based Invoice Configuration > Parked Invoice Processing Configuration > Rollout Criteria > Event Linkage for Processes (Non-PO). Maintain the FM

2. Check the "Linkage Activated" checkbox to ensure that event linkage triggers the PO parking Proces

I hope this was useful and gave an insight into Rollout Criteria and Event Linkages

" Sorry I couldn't add screen shots to the post  "

Hello All,

We all know the use of the command field you see in the upper right of the SAP screen: here is where you enter transaction codes!.

As the SAP help of this field explain the use of this field, here what you can do with this field

You can execute the following commands in this field with Enter:

•     To call a transaction

•     To end the current transaction, Enter: /n.

•     To delete the current session.Enter: /i.

•     To generate a session list, Enter: /o.

•     To end the current transaction and return to the starting menu, Enter: /ns000.

•     To log off from the system, Enter: /nend.

•     To log off from the system without a confirmation prompt, Enter: /nex.

This been said, there  is a ‘hidden’ function of this command field in SAP that I am pleased to present to you :

As I am posting this in financial space, I will present some functions that you can use while displaying a FI document that may be useful, use them as shortcuts :

Enter “AH” without slash or anti slash, in the command field while you are in displaying mode of a FI document FB03 :

It will send you to the function : document change history right away.

From the overview display, enter ‘AZ’ : it will display the first line item (no need to double click on the line item any more )

Ah now you need to switch to change mode, do not use you mouse, just type “CHAE” in the command field.

Do your changes,  to save, enter AE in the command field, done!

Need to go to next line item, Enter ‘Z+’, need to go back ? ‘Z-‘.

You want to display the additional data of the line item ? enter ‘ZK’, here you are !!!

And to change display view to general ledger view, use ‘SV’, To go to another ledger, enter ‘LR’

Ok let’s go back to display view, enter ‘SU’

To display the TAX data, enter ‘ST’

Withholding tax data ? enter ‘QS’ for this purpose

Need to go back from line item display to overview ? type AB in the command field.

Want to check if there is any objects (document, files, scans…) attached, just type ‘OBAZ’

But let’s check the relationship browser as well, go and type “DBR” on the command field.

Or maybe just the accounting document related ? type then ‘ZREC’, suppose the is a FI document generated by another module (MM, SD, HR, CO..), you can display the original document by entering ‘ZBEL’

Any texts related to the document (correspondence, note, Payment advice information) ? just enter ‘TEXT’ (this one is easy…) to display all document’s texts.

There is no correspondence ? you need to generate one ? enter then ‘KORR’ and you will be prompted to choose you correspondence.

But this is a payment document, and you need to check the payment usage ? easy, just enter ‘EPOS’ and there you go.

This document was reversed, ok to display the reversal document, you can enter ‘CA’

To display the header of the FI document, enter ‘VK’

And you need to jump to a line item, enter ‘ABZL’

Or another FI document ? enter ‘NB’

at the end you want to print your document, use ‘PRNT’ to do so

I suppose this codes existed to avoid using the mouse, but some of them are very useful and it is always exiting to find hidden functionalities inside SAP, there is a lot more like this ones…

Have fun

Tamim

Hello Community

The 2nd set of 20 FICO Tips in this series is right here. For those who missed the 1st series, here is the link. 20 FICO Tips - Series 1

Special thanks to Aleksey Tkachenko for providing latest insight on one of the points shared in Series 1

THANKS for reading the document. I invite your suggestions, feedback

THANKS to all those who read, shared, gave their valuable feedback, rated & liked the 1st document in the Series 20 FICO Tips - Series 1

Thanks & Regards

Ajay Maheshwari

Summary

While there are many documents over the internet that guides us to configure the asset accounting starting from maintaining the chart of depreciation to passing asset transactions. However for maintaining the group asset specifically for the Indian scenario (ie as per Income Tax Act 1961) , details available are quite fragmented. Hence I have prepared this document in an effort to sum up the steps that needs to be followed for creating group asset and assign it to the Tax Depreciation.

For Indian context, we need to have two depreciation areas, one will be used for the depreciations being followed at company level (in SLM method). The other depreciation area (15) required to meet the statutory requirement of following the WDV method at Group level, hence we require group asset.  There are depreciation rates that authority provides, however  I will focus more on the config part. Yes , I have worked with two depreciation keys accordingly. Following steps.

Create Asset Class (OAOA): Apart from maintaining the asset class for individual asset, you are also required to configure additional asset class which will be used as group asset. You can create them by copying.

Indicate asset class as Group (OAAX)

Here I have to indicate which asset class has to be considered for group asset.

Indicate Tax depreciation area (15) against the group asset (OAYM)

Note: This step is necessary otherwise system will not allow you to create the group asset. It will throw error as no depreciation area maintained for this group asset.

Create the Group Asset (AS21)

You need to create as many group asset as the number of asset heads you have. Heads like Plant & Machinery, F &F. I have worked on creating Motor Vehicle.

Make Group asset field mandatory in AO21 for screen layout 1000, make it mandatory.

Map Individual asset’s dep area with group asset (OAYZ)

Select the tax depreciation area and click on Edit ->Change Field Contents

Select group asset and press OK.

Create Normal asset (AS01)

Now create the normal asset, remember, when you try to save, it will open the following screen with the below message. Enter the group asset here and then save again. This field can be normally located when you check the Tax depreciation inside the Depreciation Area Tab of AS01 screen.

Other Checks:

OADB Check: Since Tax depreciation is only for reporting purpose, hence we need to have entry posting in this area. Hence you can keep the following settings.

OABC Check: Since in Dep area 15 theres no actual posting happening, hence it has to derive the values from the Book depreciation level. Hence we should have the following maintenance for the derivation.

After Posting Asset acquisition entry F-90

AW10N screen displaying the year wise depreciation in SLM method with 17 years as the useful life.

AS23 Screen displaying the asset depreciation as per IT Act 1961 in WDV method. Depreciation is at 9.5%

I hope you all find this document of some value, any feedback is always welcome.

best regds

Subha

With the encasement of the Finance Bill 2016, Krishi Kalyan Cess @0.5% will be levied on all taxable services.  So from 1st june 2016 effective service tax rate will be 15%. The tax break up will be:

In addition to that CENVAT credit will be applicable for Krishi Kalyan Cess. So total CENVAT credit available on service tax will be14.5%.

Now we have to map the cess in SAP. For that SAP is already released the note 2319788. In that note the customization document also provided. Here I want to brief about the configuration maintained in it in the receivable (A/P) point view.

Basically service tax categories are in 2 ways.

1. Full reverse charge :  Under full reverse charge the service receiver is liable to pay service tax and

2. Partial/joint reverse charge:  In this Mechanism, both the service receiver and the service  provider are liable to pay service tax at specified percentage 

                                              of the value of taxable service.

I am not going in depth above topic. Now come to configuration point of view in SAP. In the customization document the below conditions have been created.

1.   JKKP - IN: AP KK Cess - 

     The above condition will use for full reverse charge

2.   JKK1 - IN: AP KKC RCM

      JKK2 - IN: KKC RCM Offset

    These 2 conditions will use for partial reverse charge

In addition to that the below account keys are created for posting to GL accounts

1  .KP1: A/P KK Cess Tax - Is used for full reverse charge

2. KP2: A/P KKC RCM  & KP3: A/P KKC RCM Offset - These keys are used for partial reverse charge

As I already mentioned CENVAT credit available for the KKC. For that we have to create a KKC receivable a/c  and assign it to the keys KP1 & KP2 in OB40. In addition to that create KKC payable a/c and assign it to KP3.

When you make invoice posting,after done other configuration mentioned in the document. The system will pass below entry in 2 cases:

1. Expense A/c Dr

    Service tax receivable A/c Dr 

   Swach Bharat Cess A/c Dr

    KKC receivable A/c Dr

    Vendor A/c

2. Expense A/c Dr

    Service tax receivable A/c Dr 

   Swach Bharat Cess A/c Dr

    KKC receivable A/c Dr 

    Service tax payable A/c Dr 

   Swach Bharat Cess Payable A/c Dr

    KKC Payable A/c Cr

    Vendor A/c  Cr

In case if the company is EOU & SEZ scheme, then it cannot take CENVAT credit. In that case the KKC should be posted to separate expense account or distribute it to relevant account. The two cases I have mentioned below:

1. If we want to post it to separate expense account, then assign the expense GL account for the keys KP1 & KP2 in OB40.

2. If want to distribute it to relevant expense, then assign the key NVV to the tax conditions JKKP & JKK1 in the tax procedure in OBQ3.

However, we can map partial reverse charge under withholding tax also. The configuration will share in another document.

KKC configuration in withholding tax

Please go through the document and share your valuable feed back.

Thanks  & Regards,

Mukthar Ali N

In continuation to my last document Krishi kalyan Cess configuration ,I want to share configuration of KKC in withholding tax for partial service tax under reverse charge mechanism.

1. Create a w.h.tax type at invoice posting

2. Create a w.h.tax type at payment posting

3. Create w.h.tax  code for the above 2 keys.

4. Define formulas for calculating w.h.tax for the above tax types.

5. Assign the tax type to co.code

6. Then after create the below GL accounts in FS00

    1. KKC Payable

    2. KKC Receivable

    3. KKC expense (If the company is not eligible for CENVAT credit)

7. Assign the payable GL account for the w.h.tax type & tax code in OBWW

8.Assign the receivable or expense GL account for the w.h.tax type & code in OBWO

9. Assign the above created codes in the vendor master

10. After done the above configuration, post the invoice.

Please share your valuable feed back on it.

Thanks & Regards,

Mukthar Ali N

Some times after creating a remittance challan, the system wont show the TDS related information. In that case if we do the below configuration settings, we will get the information. Here I brief about the impact before and after configuration settings.

After we create a remittance challans through J1INCHLN, the system will display the below screen shot.

In the above screen shot, the system is not displayed any TDS information. Because of the below configuration

is missing. If we do below configuration, then the system will display the details

Here we have to activate the check box for the co.code. After that we have to activate the flag for the co.code

in the table J_1IEWT_ECFLAG by SM30.

Once we have done the above configuration the system will display the TDS information as shown below:

Furthermore if we want to break up the TDS information as Basic and Cess, then you have to do the below

configuration in the table J_1IEWTECESS by SM30.

Here you have to maintain all cess w.h.tax types & codes for the country with flag.

Once you done the configuration, it will display the information as shown below:

Note: At present there is no education cess is applicable in India. So we can use this field for Swach Bharat

Cess & Krishi Kalayn Cess.

Please share your valuable feed back on this.

Thanks & Regards,

Mukthar Ali N

Hello Community

The 3rd set of 20 FICO Tips in this series is right here. For those who missed the initial two series, here are the links.

20 FICO Tips - Series 1

20 FICO Tips - Series 2

THANKS for reading the document. I invite your suggestions, feedback on the same. Hope you will bless this document by leaving your valuable comment

It is very special to know that this knowledge series is widely appreciated by the community, as evident from the feedback received from you all. Both the earlier documents in the series have received close to 3000 views and ~ 5 star rating and appears as one of the Most Liked content over the past 3 months. Thanks for the honor!!

Regards

Ajay Maheshwari

After Implementing the note 2035657, Account ID Field in transaction screen will be available as an input field . If the user wanted to select the value from this filed we have to ensure the the table T042IY is filled with the appropriate value.

Please check the required settings required to maintain in F-58 screen.

Please refer the sap note and recent sap discussions

F-58 is picking up check lot only from one Account ID and ignoring other Account IDs under same house bank

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361…

OBCY: FI Summarization rules, for Ref transactions, the Table-field combination drives the summarization rules in accounting document posting. These rules apply to all company codes or org data in the same instance

Snapshot of OBCY for ref transaction VBRK

Let us say user wants Granular visibility at the GL level for reporting purposes for a particular company code .Based on the existing summarization rule if a Billing document is created with 2 sales order, material and unit of measure being the same, the existing summarization rule would post one GL line for both the sales orders in the Billing accounting document through the SD-FI interface.

Billing With Summarized GL

Dynamically we can split the Revenue account for each sales order by updating the assignment field or the text field for each of the GL  with unique values for each document .

We can either use a BADI “AC_DOCUMENT” or SD Exit “SDVFX004” to update the values through the custom code

Billing with Split GL lines for each order 

Similarly we can use BADI AC_DOCUMENT on the MM-FICO interface to split GL lines according to requirement  overlaying the summarization rules Example : for ref transaction MKPF , by dynamically updating the assignment or the text field

This being my first post on SCN, hopefully folks would find this useful

Hello Friends,

I recently encountered one issue related to open items selection -- free selections screens provided by SAP standard programs like f-32, f-28, f-44, f110 and f150. I found an interesting aspect which I would like to share:

Problem Description: In open item selection screen in f-32 customer would like to have more selection fields.

In standard SAP screen the fields are limited as below:

If we select document number:

Customer wanted to increase the number of selection fields.

Solution: Generally the first instinct is that for this kind of problem would be that modification will be needed with the help of ABAPer

However, in certain cases a more simple solution is available but might be overlooked because of the trickiness of SAP interface.

In cases like f-32,f-44, f-28 , f110 free selections you do not need any modification to the code.

You must try following before going for program change:

Simply enter (use) all the selection criteria and press enter. For example if you have chosen document numbers –

Then press enter. You will get below message:

This means the entered selection criteria are already filled in a buffer table and you are free to give further criteria !! 

Hence in such cases if you can inform the customer. If customer still persists that he needs more input fields in single screen then the modification required is only in GUI part of the program.

Exception: In case of the APP free selection screen this does not work. Hence in that case you will need to have more modifications in the program (F110_FLDTAB_1820)

Hi Folks,

This document will be helpful to one who is new to SAP FICO like me and want to do hands on Automatic Payment Program(APP) tcode F110.

3 concept are covered in this doc which are as below :

1. General APP scenario.
2. Installment payment scenario
3. Multiple partial payment

with detail of check and payment advice working.

Below is my work and understanding of APP run:

Automatic Payment Program (APP):APP is a tool that will help users to manage payables.

SAP gives users the options to automatically:

1. Select Open(Pending) Invoices to be paid or collected

2. Payment Documents to be posted

3. Print Payment Media or generate EDI

The APP has been developed for both national and international payment transaction with vendors and customers, and handles both outgoing and incoming payments.

Before running APP we need to do configuration for APP.

Steps for Configuring APP are :

1. Setup payment method per country

2. Setup payment method per company code

3. Setup all company codes

4. Setup paying company code

5. Bank determination

6. Assign payment method to vendor account

Case 1: General APP scenario

Step by step process:

Step1:  Go to transaction ‘FBZP’ or  SPRO pathIMG -> Financial Accounting(New)->Account Receivables and Account Payable->Business Transactions->Outgoing Payments->Automatic Outgoing Payments->Payment Method/Bank Selection for Payment ProgramOr we can get below screen by running ‘F110’ and under environment ‘Maintain Config’.  

We  get below screen ‘FBZP’ to maintain configuration for APP

Click on Company Code (OBVU)

x

`Click on New Entries and Enter Company Code ‘ZJDC’, Paying Company Code,Sending Company code is not entered if paying and sending company code are same.Paying and receiving company code should have same company code currency.On saving , new customizing request is created .

Step 2: Select on Paying company codes

Click on New EntriesEnter Paying Company Code and Minimum incoming and Minimum outgoing Payment.Double click on Form to enter Payment Advice form and Sender details to enter sender details

Click on Save, Customization request created and paying Company code data is configured

Step 3:Now Select Payment Methods in Country

Click on New Entries and give below details:Click on Save and customizing request is created

Step 4:Select Payment methods in Company Code

Click on new entriesNow enter below detailsClick on save and we are done.

Step 5:Click on House Bank, or Tcode FI12 if House bank is assigned to company code than go to ‘Bank Determination’Enter Company Code ZJDC

Click on New entries

Click on Save 

is configured

Go to FI12 and maintain House Bank, Account ID, Bank Account Number and GL for Bank posting

Click on Save:

  and House Bank is configured for Company code.

Table: T012

Step 6:Configure Bank determination for Company Code

Create ranking order for Paying Co. Code ZJDCOn Saving    bank determination is done for ZJDC and for bank SCB.

Now Click on Bank Accounts

On Saving bank accounts has been configured.

Now Click on Available Amounts, press New Entries:

On Saving,  and Available Amount for outgoing payment has been defined.

Value Dates:

Expenses/Charges

Step 7:Now need to assign payment method ‘C’ for Vendor.For this go to tcode ‘FK02’, assign payment method ‘C’Now Before APP run, we need to have a vendor open items, for that we need to create vendor invoice in transaction F-43.   Enter Posting key 40 and GL account 310123 to pass value to gl accountIn the next screen type * in Amount and + in Text field it will fetch previous value automatically.Click on Simulate, in Document Menu Bar (Shift+F9):

Next Screen is as below

Now to Post document, click on or go to Document and Select Post

Error:

Error is rectified by assigning number object 19 to ZJDC company code, Tcode FBN1

Now we can check vendor open items in tcode ‘FBL1N'

Step 8:Now we can go to Tcode ‘F110’, as APP Run and any 5digit alpha-numeric characters as identification.

In the Parameters Tab, We have to define the following

1. What is to be paid – Docs. Entered Up to

2. When will the payments be made – Posting Date

3. Which company codes will be considered – Company Codes

4. What payment methods will be used – Payment Methods

5. Next payment date6. Vendor Accounts for which payment has to run

Save the Parameters entered:

Now click on Proposal

We can check the proposal log  by clicking on button

We can Edit proposal by clicking

if want to change payment for Vendor

Now click on payment run on status screen , check on popup

Status is Payment Run has been cancelled

Number range 20 assigned in company code ZJDC, via  FBN1

For ZP document type NR: 20, to confirm go to tcode OBA7 or table T003

OBA7

Now again doing and it is successful

We can see the payment detail in FB03

No open line items in FBL1N

Note: earning account 759999 is fetched from

Tcode: OBXU   

Case 2:Automatic payment program for vendor with Installment payment term:

For making Installment payment:

Step1:First define a payment term in OBB8 with below detail

Step2: Now go to tcode: OBB9

When  creating vendor Invoice F-43(FB60 for multiple line):Use payment term ZTIN for installment payment

For Next line item

Now Simulate, Shift+F9

Now post,

FBL1N open item entry

To give check print program, assign SAPScript name in FBZP ‘Payment methods in Company code’ as below:

For Payment advice give sapscript name in ‘Paying company codes’ under FBZP

Now go to t code F110 and Set parameters

We have to create check lot for paying company code in FCHI

Now proposal log in F110

After payment run

Go to FBZ5, enter printer for check printing and advice printing

Now Print,  Ctrl+P

Now we can go to SP02 and check log printingOne for payment advice and one for check as we have entered printer name in both in t code FBZ5

Note: We can restrict number of rows in check printing (FBZP , Payment method in Company Code)

If payee lines are less than installment payment line.As in below example we have Installment term ZTIN which have 3 payment term (OBB9)But Payment advice control restricted to 2 rows in Payment Method Company code ,FBZP

Note: Uncheck Individual Payment in Vendor Master data, if not than 3 separate payment document will be created per payment term and 3 separate checks will be printed.

In FBL1N, one payment document is created

In FBZ5, for Doc 2000000016 only 1 check is printed and detail for line item isin advice

Check is not having line item details for payment,

Payment advice has detail of payment as per payment term

If restricted to value is more than equal to installment term, in this case 5 > 3 installment terms

Check printing will have line item details and no need to give separate Payment advice :

Advice print, in this case not needed but still can be printed with line item details.

Case 3: Multiple Partial Payment from an invoice through APP(F110)

1. Create Special GL account for Down payment request(FS00):

  2. Assign special GL account to Vendor reconciliation account(FBKP):

GL 399999 detail, recommended to have line item display checked

Click on

Use OBXT to facilitate payments for special GL Indicator “P”

Use FBZP to facilitate payments for special GL Indicator “P”

Post vendor invoice using FB60 or F-43

In FB03

General Ledger view of doc:

Execute F-59 to generate request for partial payment with reference of invoice 1010:

FB03 to check document number 100000000

Use the Tcode FB02 to block Main Invoice number 1010 so that payment can’t be made in full else mistakenly can be done

And click on Save

Now Payment for 1010 invoice is blocked

Run F110 to make multiple partial payment

Document 100000000 is open to pay as partial payment for invoice 1010

There is payment block for Document number 1010 so payment proposal shows error

Now Payment run

Payment log

After payment run vendor line item FBL1N

Again execute F-59 for to generate request for 2^nd partial payment

Click on

Document 1000000001 was posted in company code ZJDC

FBL1n status

FB03 to check doc number 100000001

Run APP(F110) for 2^nd partial payment

Payment run log Document 2000000019 is created for payment

FB03 for 20000000019

Now FBL1n

Now use FB02 to unlock payment block for document 1010

Now run F110 for final payment run

Now go to FBL1N as payment block was removed from Doc 1010 all payment is done to vendor for invoice amount 800 USD

Now go to FBZ5 and generate check for all doc 20000000018,2000000019 and 2000000020

Payment doc 2000000020 will have detail about all payment made as per request and final settlement of 300 USD