This documents explains the customization and how system calculate interest when we select the check box Open and all cleared items and open items and items cleared with a payment.

Intoduction:

Every company has their own pre-defined policies/terms and conditions towards the collection of the debts from the customers. These policies/terms and conditions depend upon the legal environment that exist in the countries where the company carries on its operations. One of the prominent policy/terms and condition would be to have an interest clause in the sales invoice to levy interest on the receivables.

The purpose of this document is to communicate to the readers the process of charging such interest on the receivables to the customers and posting an accounting document on the customer accounts.

The process followed for calculating the interest calculation on customer accounts would be to execute the interest calculation run for a defined period for defined accounts. The system would calculate the interest based on the customization maintained related to interest indicators. The calculation run can be executed further to post an interest document in the customer accounts. For correspondence with the customers, the same run can generate an output document (like invoice) which contain the amount of interest charged and the receivables towards which such interest is charged.

Interest can be calculated on customer and vendor accounts in two ways:

Account balance interest calculation: This calculation type calculates interest on the balance of the customer on the interest calculation day. If the customer has a debit balance (receivable) then the debit interest rate will be taken into consideration and if the customer has a credit balance then the credit interest rate will be considered for calculation.Account balance

Item interest calculation: This calculation type calculates interest on the line items for a customer. A customer may have open line item as well as cleared line items. Interest can be calculated for both open and cleared line items or only on the open line item.

Customization Transaction Code and Path given below

1. Interest calculation customization done at client level
2. Assigning interest calculation to customer master data at company code level

T.CODE OB46 Define Interest Calculation Types

Define time dependent interest terms T.Code OB81

The below Setting done in transaction code OB82

Selected interest term with Open and all cleared items.

Once all the customization comleted assig at customer master data .

Same interest indicator we use at dunning customization :

At dunning this indicator only becomes effective if there is no interest calculation indicator entered in the master record. Otherwise the indicator in the master record has priority. If there is no indicator at either level (dunning procedure or master record), i.e. 'BLANK' is entered, then no dunning interest is calculated by the system

Invoice Entry posted

Interest run executed on 31.07.2013 in test mode

UN check Test run and post the document

Check the customer balance and customer master data

Last key date updated

Case Two:Credit memo posted

Now customer having negative balance

Interest executed in test run  mode on 31.08.2013

Even though the customer having negative balance , interest will be calculated on open line items as per customization.

Case 3:

Changed the customization from Open and all cleared items to open items and items cleared with a payment.

With this option you will come to know what happen when partial payment received and how system calculate interest.

Now posted incoming payment with 215.59 and clearing the invoice document EUR 115 and interest document EUR .59

Current balance:  credit memo value 200 EUR+ 100 Excess payment received = 300 EUR

Interest executed in test mode on 31.08.2013

In the above case system correctly calculating interest on 115 EUR from 01.08.2013 to 15.08.213.

System calculates the interest even the customer having total of negative balance.

Case 4:

1. Posted invoice with EUR 400 on 29.08.2013
2. Clearing posted with EUR 400 with total credit amount EUR 300 29.08.2013

Customer balance

Now  Clearing of invoice 400 with excess amount received of 300

After clearing the Current balance of that customer is 100 EUR

Executed interest and document posted 31.08.2013

Case 5:

Changing customization once again to Open item and all cleared items. and removing the check box option only calculate interest on debit item.

See now how system display interest.

Credit memo Invoice posted 01.09.2013

Interest executed on 30.09.2013

in the above case you can view interest calculated on credit line item 3% and debit line items with 8 % as per customization.

Hope with you learn how system calculate interest on credit and debit line items of the customer .

This project is working for providing support to IS- SAP Team. This project provides support to all organizations functions i.e. Billing, Tax, Finance etc. Author belongs to SAP FI support team and it provides support to finance users. All existing finance processes are being supported by team. Most of SAP FI modules like GL, AP, AR, Asset, Fund management, Treasury, banking are being supported by team. SAP FI support team dedicatedly works in order to provide smooth functioning of finance department. An extended support is provided during month and quarter ends apart from normal support work.

Introduction: This is to understand and to learn how to add Brazil postal codes to the standard SAP system in order to pay account payables invoices which carry Taxes line items.  As every county has a different rate of tax and different counties pay different kinds of taxes, hence it becomes necessary for SAP to know from which region the business transactions originates and the region which deals or purchases the goods or services. We will delve into jurisdiction code which is a code used for determining tax rates in Brazil; it controls which tax authorities must be paid for any particular transaction.

The tax jurisdiction code is comprised of the following two parts, the tax region and municipal region, the Tax region comprises of 1 to 3 characters while the municipal region, which comprises of 4 to 16 characters.

Procedure:

Procedure is to add Brazil postal codes a procedure for a country version. You need to configure this as this supports Vertex tax calculation procedure and enables payment of invoices.

Assumptions:

Tax configurations in following T. codes:

• OBBG
• OBCO
• OBCP
• FTXP
• OBCL

Have already been set up.

Configuration:

We need to configure following settings: -

• Please Check whether the given postal codes were available in production systems, generally the postal codes won't be available, Some times couple of codes will be available with other Jurisdiction codes.

• Ensure the user/business has provided the following information:

• Region
• From post code
• To post code
• Jurisdiction code

Please note: the text field will populate by itself.

• Please add the given postal codes in development systems by following the below path.

• We can add the postal codes directly in the table " J_1BTREG_CITYV". We can add the postal codes through -> SE16 -> table name. Please be informed this is not the correct process. We have to add through the path mentioned above.

• Incase of any ambiguity on the city of a particular postal code, Please check the below link for clarification.

http://www.correios.com.br/eng/sys/cep/default.cfm

• Please enter the postal code, and click on search, it will display the city name which is associated with that postal code. This can be cross-verified with the data available in our SAP system. Incase of deviations please get it clarified with user.

• Use country key: br
• Define Tax Jurisdiction Codes

• Here define the jurisdiction code as per the country key..
• Next assign the postal codes
• Please view the below screen shot and click on the tab – ‘New entries’

Post this, Add the following:

• Region
• From post code
• To post code
• Jurisdiction code

• And hit the enter button after each line.
• After adding all the lines, click on the save button and create a transport request as per the convention followed by the customer’s standards.
• Request Basis team to move configuration transport request to all test systems.
• Test the data in Integration systems and Quality systems
• Procure UAT after sending screen shots from test systems
• Once you receive the UAT create a change request
• Post implementation, send screen shots to the user and ask for closure of the ticket.

Purpose

The purpose of this document is to document the entire Configuration required for Budget Availability Control (BAC) including Budget Profile and Tolerance Limits. At the end of the document, examples of BAC response based on the tolerance limit set are documented.

General Information

The configuration for BAC can be divided into two steps

- Maintaining Budget Profile

- Defining Tolerance Limits

Maintaining Budget Profile

Detail Configuration steps with screen shots for Budget profile are listed below:

Go to Maintain Budget Profile using the Transaction code or Menu Path stated below:

Select “New Entries”

• Profile – Budget Profile Enter the name for the new Budget Profile, say “ZCAP”

• Text – Description for Budget Profile

Enter the Description for the Budget Profile, Example -> “Profile for Capital Projects“

• Timeframe: Based on the business requirement, specify the number of years in the past/future you would like to plan/budget projects for.

For the purpose of illustration, the budget profile is maintained such that the Budget can be maintained for 5 years in the past/ 5 years in the future and the start year (current year) as the reference point.

• Total values (Indicator): Check this indicator so that overall values can be maintained for budget.

• Annual values (Indicator) – Check this indicator if business prefer to maintain the budget on annual basis.

• Representation :

• Decimal places and the Scaling factor would help in controlling the layout of the filed group values that have constant units.

• Decimal Places - Number of Decimal Places (say ‘2’ )

• Exchange Rate Type – M

Maintain the exchange rate type that would be used for the BAC calculations.

• Program Type Budget - Program type for budgeting In case of Investment Projects, this field will be significant, as this will ensure that WBS elements with a given budget profile cannot receive overall or annual budgets unless the WBS element (or a WBS element above it in the hierarchy) is assigned to a program position of an investment program with the correct program type entered here.

Select the Program Type for the Budget Profile, example “Z001”

• Activation Type – Availability Control Activation Type

This Field determines whether and how availability control should be activated.

There are three activation types:

0 = cannot activate: This activity type may cause an already active availability control to be deactivated.

1 = automatic activation when budget is assigned. Upon selecting this activation type, at least one tolerance limit should be maintained for the budget profile.

2 = background activation when percentage of consumption is exceeded For the Project used in this illustration, as we want to activate Budget Availability

Control when Budget is allocated, maintained the Activation Type as “1“

• Usage - Usage in % for background activator.

- Use this indicator, only when the activation type ‘2’ has been used. By maintaining a percentage value in this field, say 50, the system will activate BAC when the assigned funds of the WBS is more than the 50 % of the budget available on the WBS. Since we have opted for Activation type ‘1’ – Automatic activation during Budget allocation, this usage field is left blank.

• Overall- Availability control against overall value.

- Select the Overall indicator so that the budget checks would be done against the Overall budget values and not against the annual values.

• Object Currency (Indicator) - Availability Control in Object Currency

- In case if business prefers budget checks to be done against the Object currency values, only then check this indicator.

• Releases(Indicator) - Availability control against releases

- If the business requirement is such that the budget is released as and when required and the budget check accordingly should be for the released budget

only, then check this indicator. If the Budget check needs to be done for the entire amount budgeted, then leave this indicator deselected.

• Budgeting Currency-

- Controlling Area Currency(Indicator) - Budgeting/Planning in the Controlling Area Currency

- Object Currency (Indicator) - Budgeting/Planning in the Object Currency

- Transaction curency (Indicator) - Budgeting/Planning in the Transaction Currency

Select the Controlling Area currency.

• Save the Budget Profile.

Result

Configuration of Budget Profile is completed for which Tolerance limits are to be set.

Example

Below is the screen shot for Budget Profile ZCAP as an Example.

Define Tolerance Limits

Tolerance Limits are set for defining what actions are to be taken when the Budget is overrun. Example: Warning will be shown if the Budget Exceeds 70% of Budget available. Warning with mail to the Person responsible when the Budget Exceeds 90% of Budget available. Hard stop Error will be shown if the Budget Exceeds 100% of Budget available. Different Budget Profiles can have different Tolerance settings.

Detail Configuration steps with screen shot for Tolerance limits are listed below:

• Go to Maintain Define Tolerance Limits using the Menu Path stated below:

Select “New Entries”

• COAr – Controlling Area. Enter Controlling area.

• Prof. – Budget Profile

Enter Budget Profile for which you want to set the Tolerance Limits. In this example, “ZCAP”

Tr. Grp – Tolerance Group

Tolerance Group is the Activity Group for which you want to set the Tolerance

limits.

E.g. Activity Group 00 – Purchase Requisition, Tolerance settings for this activity group will be applied only for Budget overrun due to Purchase Requisition.

Below is the list of allowed Activity Groups:

Select Activity Group “00” for setting Tolerance limits to give warning message and an email when PR exceeds 90% of Budget.

• Act. - Availability control action

This field indicates what action is triggered if the defined tolerance limit is exceeded.

Enter “2” in this field as we want a warning message and an email when PR exceeds 90% of Budget.

• Usage - Usage rate in %

The "usage" represents the ratio of funds commitments to the budget, expressed as a percentage. If this value is exceeded because of budget reductions or assigned funds in commitments which are too high, the specified action is triggered.

Enter “90” in Usage Field.

• Save the Tolerance Limits for PR for 90% Usage.

• Below is sample of business requirement for Tolerance Limits for below Activity Group and Budget Profile combinations.

Result

Tolerance Limits were successfully set for Budget Profiles and Activity Groups.

Example

Below is the screen shot of a Tolerance Settings for Budget profile ZCAP when budget exceeds 90% and 100% of WBS Budget.

Examples of BAC actions:

• Created a project (FS00141) and assigned the WBS FS00141 to an Investment Program.

• Distributed the budget to the project using transaction IM52 for a value (USD 1000.00).

• Since the activation type maintained for the budget profile ZCAP is automatic activation upon budget allocation, the status of the WBS for which the budget is

distributed will now be BUDG AVAC

• WBS Person responsible is maintained on the WBS

Now create a PR for USD 901.00, which is 90.1% of the available budget (USD 1000.00). In this example, created PR for qty 1, hence the valuation price is same as the PR amount.

Check that the account assigned object is the WBS element for which the budget has been maintained.

• If the requisitioned tries to save the PR, then system will pop-up the below messages

• Once the PR is saved, a warning mail will be triggered to the person responsible maintained on the WBS. Below is the screen shot of how the message will look like at the SAP Business Workplace (SBWP) in the inbox of the person responsible maintained on the WBS.

• In the above message, the following details can be noticed.

- PR number which has triggered this warning message

- WBS FS00141 for which the PR has been assigned and for which the budget check was done

- Assigned funds are 99.00 USD less than budget which means the available budget on the WBS is now 99.00 USD

• For this same WBS copying the above created PR 20001251, if the Purchase Order is tried to create for USD 1001.00 which is a dollar over the budget allocated, the system as per the tolerance limit set (Hard stop error when assigned funds exceed 100% of available budget) should throw a hard stop error.

• With reference to PR 20001251, create a PO for USD 1,001.00. Check that the WBS is the same used on the PR and budgeted FS00141

• When the buyer, tries to save the PO, the following message window will pop-up and prevents from saving the PO. The message displays the amount by which the available budget exceeded. (USD 1.00)

• Similarly in case of the other activity groups, BAC would trigger appropriate action based on the tolerance limits set.

Financial Contract Accounts and Receivable SAP FI-CA:

• SAP FI-CA is the response to market requirements for receivables management for mass data processing industries and for high system integration
• FI-CA covers all standard accounts receivable and payable functions. Although FI-CA provides new functions, process enhancements for account receivable management, and a high degree of flexibility in functions, it does not replace the SAP classical application FI-AR

FI-CA represents an alternative sub ledger for industries with

• Large volume of documents to process
• Large volume of business partners
• Industry- or customer-specific business processes that need to be
• seamlessly integrated into the customers' system architecture
• Component Industry Contract account Contract Explanation

Availability of FI-CA: Previously, FI-CA was only available in the following SAP industry solutions:

• IS-T Telecommunications
• IS-U Utilities
• IS-M Media
• IS-PS-CA Public Sector( This component is also known as PSCD)
• FS-CD –Industry solution for Insurance (Financial services collection and Disbursement)

The component was not available for customers outside of these industries Now FI-CA is also available as an industry-neutral version FI-CAX.

Technical Highlights of SAP FI-CA

Master Data Management in FI-CA

Business partner: A business partner is a customer within FI-CA The business partner contains central data such as name, address, and bank details All invoices and payments are posted to a contract account, which is assigned to a business partner

Contract Account: The contract account contains control information like payment methods, payment conditions, or dunning Procedures

Purpose of Contract Account

• Object for which open item accounting takes place
• Contains application-specific business partner data

Contract Object: A contract object is an optional master data object that can be assigned to a contract account and business partner the contract object allows for the segregation of receivables below the contract account

A single business partner can have multiple contract accounts in FI-CA In addition, SAP offers a third master data layer within FI-CA This third object is called contract or contract object The purpose of this object is to further distinguish the receivables within a contract account This is necessary if you need to group receivables from multiple contracts into one contract account and still want to separate the receivables.

One interesting feature within master data management is the ability to create user-defined fields or new tabs and combine screens using the Business Data Toolset (BDT) without any modifications BDT maintains and supports transaction data and master data.

The purpose and the functionality of the contracts vary within the different industry solutions; however, the concept is always the same See below table for a list of examples of contract accounts and contract combinations within the different industry solutions.

Document Structure

Documents structure in FI-CA is structured with the minimum number of fields required with repetitive structures for installments, sub-items for partial payments this gives the following benefits:

• Reduced memory space required for storing open and cleared items
• Enables high performance processing of critical business transactions –posting, dunning, payment

Following are the Parts of FI-CA document

• The document header contains general data for the accounts receivable/payable document such as: the document number, document category, document date, posting date, currency, and reconciliation key Data on the person making entries and on the origin are stored in the administrative data of the document header.
• Data relevant to posting is stored in the business partner items: Data on the partner/contract, general ledger data (receivables account), data on the receivables amount, specifications on the due date, dunning and clearing data, cash management and forecast data, and other data.
• Information on offsetting posting is stored in the offsetting item This normally means the line items for revenue posting(s) and the tax posting line items.
• Offsetting items and tax lines are created automatically, so only the business partner items must be created.

Parallelization of mass data processing

Parallel processing is used to reduce time for processing large volume processes by splitting. Parallel processing can be used for mass processes like 

• Payment run
• Dunning notices
• Correspondence Print
• Mass calculation of interest
• Generation of Bills

Openness for Enhancements

In SAP FI-CA there is a new concept Events Using Events standard process enhancements is possible without modification

Event: Time at which an open interface exists - customers can use the option of creating and activating additional or alternative algorithms in their own function modules Events can be managed using transaction FQEVENTS,

Key Functions in Business Transactions

Key Functions in FI-CA:

1. SAP FI-CA covers all standard accounts receivable and payable functions.
2. In addition, critical business transactions for mass data processing have been improved and new functions have been implemented.

The following section gives a brief summary of the most important new and enhanced functions in comparison to the traditional SAP FI-AR in each of the following areas:

1. Posting and Documents

2. Payments

3. Returns

4. Dunning

5. Installment Plans

6. Deferral

7. Write-Offs

8. Submission to External Collection Agencies

Documents and Posting

• Represents a business transaction that results in the update in sub-ledger and general ledger accounting

• The business view of a document shows

1. 1. Document header

1. 2. Document items relevant for sub-ledger accounting (open item)

1. 3. Document items relevant for general ledger accounting

Specific Features:

Posting:

1. Documents are automatically imported from an operational SAP or non-SAP System
2. Documents can be entered and posted manually

Cross-date posting:

1. Specific documents can be posted for several dates(Receivables with recurring dates, such as installment plans)

Cross-company code posting

1. The company code is recorded separately for each line item, and not in the document header
2. This enables the user to enter items for several company codes in one document, so that a cross-company code document can be posted

Statistical items:

1. Reflect a receivable or payable in the contract account that should initially not be visible in the general ledger
2. Do not contribute to the balance of the document
3. Do not result in an update in the general ledger

• Used, for example, for:

• Deduction and down payment requests

• Statistical outstanding charges

• Installment plans

Mass changes:

The following data can be changed for several line items at once

• Payment data
• Dunning data
• Due date data
• Locks

Payments

Purpose

To create and process incoming payments

Specific Features

Payment lots:

• Groups of payments that are to be processed together (e.g.: all incoming payments contained in one bank statement)

• Lots are created by entering the data from incoming checks or bank transfers, either manually or using programs for fast input

• Using an extensive assignment algorithm (clearing control), the system processes the payment lots and assigns the payment to the related open item

• Over-payments can be posted as payments on account; underpayments are posted as partial payments

Clarification account:

Payments requiring clarification are posted to separate interim accounts and must be processed manually

A repayment can be initiated for payments which cannot be assigned to an open item

Payment program:

• Enables the creation of outgoing and incoming payments.
• Determines the open items to be paid according to the selection criteria entered for the payment run, and according to the due date of the open items
• Selects the payment methods and the appropriate bank.
• Posts the payment document and clears the open items or creates payment orders In case of payment orders, posting and clearing take place as soon as the order is confirmed with the bank statement.
• Provides the data for the payment media.
• Will be processed in parallel processes to reduce the overall runtime

Returns

Purpose

To process bank returns that may occur as part of collection procedures, check deposits, or outgoing payments

Specific Functions in FI-CA

Automatic returns processing

• Returns are processed automatically -original receivables or payables are reopened.
• Alternatively, new receivables can be posted
• Generation of any further postings that are necessary due to taxes or charges
• Automatic start of follow-up activities

Charging of bank fees

• Bank fees and any additional charges can be charged to business partners
• Charges can be posted either statistically or to the general ledger

Follow-up activities

• Changes in the item
• Changes in the contract account
• Setting a deferral date, a dunning lock, or payment lock for the reopened receivables
• Workflow connection
• Creation of information for the clerk
• Correspondence for the business partner

Activities can be defined dependent on

• Return reason
• Creditworthiness
• Tolerance group
• Number of returns

Return history

• All relevant data is recorded in a return history
• Referred to when determining creditworthiness

Dunning

Purpose

To remind business partners that their payables are overdue and to request payment

Specific Features in FI-CA

Dunning activities

Assignment of any number of dunning activities to the various dunning level, for example,

• Printing a dunning notice
• Termination of a contract
• Activating a lock

Dunning charges

• Option of calculating dunning charges using an extensive charges procedure
• The calculation rules can be specified dependent on currency and creditworthiness
• The charges and interest can be posted either statistically or to the general ledger

Dunning history

• Dunning-relevant data for each item is recorded in a dunning history
• The dunning history is referred to when determining the dunning level of an item
• The dunning history can be used at any time to provide information about the individual dunning activities

Dunning run reversal

• A dunning run can be reversed completely
• The system reverses either the whole run or the items that were not successfully posted and notes the relevant entries as being reversed in the dunning history
• Additionally, the system determines and resets the charges and interest posted during the dunning activity run and resets the creditworthiness for the customer in question

Dunning run for installment plans

• Alternative dunning run can be processed for installment plans
• Automatic deactivation of an installment plan when a certain dunning level is reached can be specified

Parallelization

  Parallel processes are used to achieve the best possible performance.

Deferral

Purpose

To defer payment for business partners who cannot keep up their payment obligations

Specific Features in FI-CA

Deferral date

• The deferral date is noted in the open item in addition to the due date
• No dunning notices are sent and no payments are collected during the agreed deferral period
• Once the deferral date has passed without payment being made, the open item is dunned with the original due date and bank collection is executed again

Deferral history

• Deferral history is kept in the document

Installment Plan

Purpose

• To arrange payment by installments for business partners who cannot keep up their payment obligations

Specific Functions

Structure

• The installment plan divides source items into several installment receivables that have a due date in the future
• The installments are posted statistically in FI-CA and are cleared when payments are made. With every installment cleared, an corresponding part of the original receivables is cleared as well
• The individual installment is included in the dunning and payment run

Installment plan set up

• Individual installments and their due dates are specified in the installment plan
• Charges can be levied for an installment plan
• The document number of the installment plan is recorded in the original receivables, which ensures that there is a link between the original receivable and the installment plan

Interest calculation

• Interest can be calculated on the installment plan

Installment plan processing

• Installments plan can be changed manually
• Due dates and the amount of installments can be changed
• New installments can be added to an active installment plan
• Original receivables will be cleared (partly) automatically, whenever an installment is cleared. Therefore, all original receivables will be cleared as soon as the last installment of the installment plan has been cleared

Deactivating an installment plan

• The installment plan can be deactivated manually
• The original receivable becomes active again and the link between the original receivable and the installment plan is deleted
• A deactivated installment plan cannot be reactivated, and no further payments can be assigned to the installment plan

Installment plan history

• The history is updated automatically for every installment plan

  Can be used to determine the source items on which an installment plan is based

Write-off

Purpose

• To write off open receivables and credits of a business partner because receivables cannot be collected or payables cannot be disbursed

Specific Functions

Automatic posting

• Written off line items are cleared and a write-off document is posted to the gain or loss accounts defined in Customizing
• Additionally, rules that specify how the tax adjustment should be made are defined in Customizing

Check rules

• Check rules determine whether and which open items can be written off (to a certain percentage) automatically
• The rules are defined with the help of a function module and allow the implementation of customer-specific requirements

Reverse write-off

• Write-off documents can be reversed, meaning that the receivables or payables become open again

Parallelization

• Write-off activities can be processed in a mass run
• Documents to be written off can be selected according to various parameters
• A simulation run can be executed before the update run for monitoring purposes

Submission to external collection agencies

Purpose

Release and submission of receivables to external collection agencies as well as management of the submitted receivables

Specific Features in FI-CA

Release and submission of receivables

Integrated release and submission of receivables while processing

• Dunning
• Write-off/mass write-off
• Manual indicator for collection order
• General submission

Receivables submission management

Managing submitted receivables in separate management

Processing incoming information

Incoming information from the collection agency can be transferred to the system -the processing depends on the way the agency forwards the information:

• In a file: Interest, charge requests, and collected payments are posted automatically
• By letter or telephone: The information has to be posted manually

Comparison of Functionalities in SAP FI-AR and FI-CA

1. Introduction

Sensitive Data Fields provides dual control function in SAP to provide more security when changes are made in Customer and Vendor Master Data records. After activating Sensitive Data Fields functionality, changes done by one profile (Ex. Clerk) in AP and AR Master Data has to be confirmed by another profile (authorized person), thereby facilitating strong control over unauthorized modification. Changes made in relevant Customer or Vendor Master Data are visible but the account is automatically blocked for payment run till the changes are confirmed.

If this function is not activated then when the master data for a customer/vendor is changed then all business processes, including for example a payment run, can be executed immediately afterwards without the changes having being confirmed regarding the 4-eyes-principles. The risk of fraudulent behavior, especially in payments to vendor and customer, remains higher than a situation where the changes of sensitive data fields need to be confirmed by another person.

2. Steps

Standard SAP offers the possibility to define sensitive fields for both customer and vendor data. This customization is at Client level and is applicable for all Customer or Vendor account groups.

Customer Master Data

      1.    IMG Path for customization of Sensitive Fields for Customers:

IMG -> Financial Accounting -> Accounts Receivable and Account Payable -> Customer Accounts -> Master Data -> Preparations for Creating Customer Master Data -> Define Sensitive Fields for Dual Control. Single data fields can be defined as sensitive.

  Similar customizing exists for vendor accounts.

     2.    Maintaining Sensitive Fields:

       Below screenshot shows various fields available for customization as Sensitive data fields.

       This includes Customer name and address, Bank details etc.

     3.    Terms of payment saved as Sensitive Field:

     4.    Changing Payment Terms in Customer Master Data:

        Existing payment term is FB00

        Terms of payment have been changed from FB00 to FB09

         Changes saved with an information message to confirm the changes

     5.    Display Customer Master Data:

         Changes available for display but the same are required to be confirmed.

    6.    Confirmation of Change:

       Changes made can be displayed by clicking Changes to sensitive fields

       Below screen provides details of changes made

       Changes have not been confirmed

     7. Executing Automatic Payment Run:

       Customer has open item (T Code: FBL5N)

        Executing Payment Run without confirming the changes (T Code: F110)

       Account was not considered for payment run due to unconfirmed changes.

Vendor Master Data

    1. IMG Path for customization of Sensitive Fields for Vendors:

     IMG-> Financial Accounting-> Accounts Receivable and Account Payable-> Vendor Accounts-> Master Data-> Preparations for               creating Vendor Master Data-> Define Sensitive Fields for Dual Control. Single data fields can be defined as sensitive.

     2.    Maintaining Sensitive Fields:

      Below screenshot shows various fields available for customization as Sensitive data fields.

      This includes Vendor name and address, Payment terms, Dunning data etc.

      3.    City and Accounting Clerk Field have been saved as Sensitive Field:

     4.    Changing Sensitive Fields in Vendor Master Data:

        City changed from Montvale to Rutherford

        Accounting clerk field was empty

        Now filled with AP

       Changes available for display but the same are required to be confirmed.

    5.    Display Vendor Master Data

          Changes made are available for display

   6.    Confirmation of Change

       Changes done in city comes under Vendor Master General Data

       Changes done in Accounting clerk comes under the preview of Company Code Data

7.  Executing Automatic Payment Run:

       Vendor Open item ready for payment run (T Code: FBL1N)

        Executing Automatic Payment Program (T Code F110)

      Vendor is blocked for payment due to unconfirmed changes.

3.    Customized solution

As already mentioned, Sensitive Data Field functionality provided by standard SAP is at client level and therefore applicable for all the customer and Vendor account groups existing in the system. Based on customer request, this functionality can be activated for specific account groups.

In our project, Customer and Vendor Account groups have been created at country level. To fulfill customer requirement, A custom table has been created to maintain the relevant account groups and Sensitive Data Fields.

Also we have added one enhancement spot in include MF02DFEX for customer MF02KFEX for vendor. Accordingly Sensitive Data Field functionality has been activated at account group level.

In this way, unauthorized changes in Customer and Vendor master data can be effectively controlled thereby reducing overall business risk.

Dear all ,

this Document very useful for all India companies :

As per Legal Requirement for all India companies should have a CIN (Corporate Identity Number - As per the Circular for Registrar of Companies Act -  1956 (ROC) , Corporate Identity Number (22 Digit number allotted  by the Ministry of Corporate Affairs) need to be incorporated along with Company details.

Configuration settings of CIN - Global Parameters

Corporate Identity Number for an India Company Code

Go to SM30 -- Table/View -- V_T001I  and click on Change  --

Click on New Entries  --   

and Save it

   Maintain the Corporate Identity Number

Path : SPRO -- IMG -- Go to Financial Accounting New -- Financial Accounting Global settings (New) ---  Global Parameters for Company Code -- Enter Global Parameters

Double click on Your company code -- and click on Additional data tab -- and Maintain CIN (Corporate Identity Number)

Please check in table data also after complete above mentioned configuration

Thanking you

Regards

Mahesh

In below blog, we have seen the configuration and calculation logic of value date.

Value date calculation logic during automatic payment process (APP)

There is step where calendar ID has been assigned to house bank and account ID.

Let us see how to configure the calendar.

This has three steps involved in this process.

1.  Creation of public holidays:

Go to t-code SCAL, select Public holidays option and click on change.

Click on create button in next screen.

Type of public holiday is defines how a holiday is determined. Select the appropriate option based on requirement and proceed.

E.G: If you want to set up Labor day (1^st May) as holiday, you can select “With fixed date” option, because the holiday date is fixed here.

Enter the day, month and select the appropriate Guaranteed option. “Not Guaranteed” means, if the fixed date falls on  week end, it wouldn’t be moved to next working day.

Maintain the public holiday attributes like sort criteria, holiday class, description etc. Other fields are self-explanatory. Click on create once you enter all the fields.

2.  Creation of holiday calendar:

Select below option and click on change.

Click on create icon.

Enter Holiday calendar ID, description and click on holiday assignment.

Select the list of holidays created from popup and click on assign.

In the next screen, you can see the holidays are assigned with validity year from 1900 to 2098. Change the validity if required and save.

3.  Creation of factory calendar:

Select below option and proceed.

Click on create and proceed.

Enter calendar ID, description, validity years, Holiday calendar ID (Created above). Select working days and save.

Validate to see if the holiday is correctly assigned or not. Select the calendar created and click on display calendar.

You can see all the years assigned in the definition.

Select the year and click on display year. You can see all the assigned holidays here. Holidays are highlighted in green. Placing the cursor on holiday date, shows holiday name.

Now Assign this calendar ID in FBZP value date rules.

Your valuable comments and feedback are most welcome

Thanks

V V

This blog is a continuation to the earlier blog "How to Trace the History of Deleted Parked Documents : Part - I"

http://scn.sap.com/docs/DOC-48771

C.2. S_ALR_87012293 - Display of Changed Documents: - This S_ALR_87012293 standard report provides a list of the document changes. And it doesn’t tell anything about the vendor or customer pertaining to which the report caters to and the value of document also. Please give the following details.

Document Type: - Parked documents

General selections:-

          Mandatory fields: - Company code, document number & Fiscal years

          Optional Fields: - Changed on & Changed by

Receiving Co. code – Useful only for Cross- CC transactions

Further Selections: - If you are aware of the data exactly so give the data here else just click the document header data, line item data.

Click Execute Icon else Press F8.

Then the following screen will appear which contains the details of co. code, entry date, entered on, doc. no., fiscal year, user name and line items got deleted.

C.3. BKPF Table- Accounting Doc Header: - This BKPF table stores data at accounting document header level. With the help of this table we can easily trace the no. of documents posted for a company code in period wise in a year or whole documents in a fiscal year. Doc. header text, date of posing, doc. status, reversal doc. no, reversal date and transaction code used to post the document, user id who got posted this document.

Go to SE16 t code and give this table and press Enter then the following screen will appear. Please give the following fields as stated below.

Mandatory fields: - Company code, document number & Fiscal years

Optional Fields: - Document type, document date, posting date and period

Here in our e.g. I am aware of the exact details of posting date of parked document, doc. Type and period so I am giving all these details.

Click Execute Icon else Press F8.

Just double click the line item then the following screen will appear.

Here please observe the document status as Z – Parked document which was deleted

C.4. CDHDR Table - Change document header: - CDHDR table is a header table to store change documents and it is a transparent table. So you cannot join CDHDR and CDPOS tables directly. Generally, old change documents from these tables are always archived for better performance of inserting data. Go to SE16 t code and give this table and press Enter then the following screen will appear. Please give the following fields as stated below.

Mandatory Fields:-

Change doc. object – BELEGV (Accounting Doc). It is changing for MM, SD and FI areas. Please find the details as given below.

Objects Value – You can get this data through FBV5 t code as highlighted below.

Optional Fields:-

Date – Date of deletion of parked document else give probable date like give this as 08/01/2013.Here in our example I just gave the details which I was known very clear.

Click Execute I con or press F8

Click the line item in order to view the details (i.e. User name who got deleted this parked document, date of deletion & T code used for deletion of parked document) in a detailed manner.

C.5. CDPOS Table - Change document items: - CDPOS table has the information for the positions of the object and it stores data at line item level. It is a cluster table.

Go to SE16 t code and give this table and press Enter then the following screen will appear. Please give the mandatory fields like Change Doc. object & Object fields as shown below.

Click Execute I con or press F8.

We can trace the details by any one of the line item.Then double click on the first line item in order to view the details in a detailed manner.

After executing the screen you can observe the Change ID- D i.e. Deleted as highlighted in the below given screenshot.

Then double click on the second line item in order to view the details in a detailed manner.

After executing the screen you can observe the Change ID- D i.e. Deleted as highlighted in the below given screenshot

Hope this blog helps to give better understanding on Tracing the history of deleted parked documents.

Your valuable feed back along with the rating on this blog is most welcome

Thanks & Regards,

Lakshmi S

This document explains the posting of a parked document, how to trace the history of deleted parked documents in SAP and number of ways to trace the history of deleted parked documents in a step by step manner. Even a beginner to SAP can easily understand this concept. All the possible ways have been discussed below with the help of an example. (A & B parts are meant for beginners of SAP as like me who doesn't have proper idea on this concept)

A. Basics

A.1. Parked Document: -You can park invoices or credit memos. This means that you enter the invoice data or credit memo data in the system and save it in a document, but the system does not post this invoice initially. You can use document parking to enter and store (park) incomplete documents in the SAP System without carrying out extensive entry checks. Parked documents can be completed, checked and then posted at a later date - if necessary by a different data entry clerk.

A.2. Advantages of posting a parked document: -The advantage of parking documents is that you can evaluate the data in the documents online for reporting purposes from the moment they are parked, rather than having to wait until they have been completed and posted. For example, amounts from parked invoices can be used for the advance return for tax on sales and purchases. Using payment requests, parked invoices can be paid punctually and without loss of discount.

B. Pre- requisites to trace the deleted parked document

B.1. Post one Parked document: - You can park invoices (FB60/ FV60) or credit memos (FB65 /FV65) as follows.

1. From the Accounts Receivable, Accounts Payable or General Ledger menu, chooseDocument Entry→ Park Invoice/ Park Credit Memo.

2. Enter the document header and line item data.

3. To save the parked document, Choose Document → Park or press the Park I con or Press F8.

You receive a message with the document number. These document numbers are assigned in the same way as the standard posted document entry function.

E.g.:- I am posting one parked vendor invoice through FB60. And later I have deleted this parked document through FBV2.

FB60:- Post Vendor Invoice

B.2. Delete posted parked document:-

You can delete a parked document as follows:

1. From the Accounts Receivable, Accounts Payable or General Ledger menu, choose

Document → Parked documents → Post/Delete.

2. If you know the document number, please inputs the company code, document number and fiscal year details and press ENTER.

If you do not know the document number, or if you want to delete more than one document, then go to Document → choose List. You can access the same tab by clicking the Document list I con or else press F5.On the next selection screen, enter the appropriate parameters i.e. document number, company code and fiscal year etc. After executing this screen then the system generates a list containing the documents that match these criteria.

3. Select the required document(s) and then choose Document → Delete.

You cannot reuse the number of a document that was deleted. Just go to FBV2 or FBV0 in order to delete the parked document

Please enter the following fields mandatorily as given below.

     1. Company code: -The Company code is an organizational unit within financial accounting. Independent accounting unit; in most cases is a legal entity. You can prepare a balance sheet and income statement for each company code. Several company codes can be set up to manage the accounts of independent companies simultaneously.

     2. Document Number:- The document number is a key the system uses to access the accounting document. This document number is unique per company code and fiscal year. When entering an accounting document, you can specify the number either manually or it can be determined the system from a pre-defined area i.e. number ranges. The relevant area of the document numbers i.e. number range is determined in each company code per document type.

     3. Fiscal Year: - The fiscal period for which this transaction is relevant.

Click ENTER then the following screen will appears

Go to Document tab -> Click Delete Parked Document option.

Then the following Pop-up will appear.

Click Yes. Then you will get a message that the requested parked document got deleted.

FB03 - Display document: – You can able to view this parked document which got deleted through FB03 t code. Please give these mandatory fields i.e. company code, document number & fiscal year. Click Enter then the following screen will appear. Please make note that Parked document which was deleted in Doc type column which is highlighted   as shown below.

Here document is displayed in list mode.

Go to Menu -> Click back button in order to get the overview screen as shown below

After executing the screen please click document header i conor press F5

Then you can find the details like document type, doc. header text, document date, posting date, ref. key, posing period, user name who got posted this doc., t code used to post a parked document and doc. status as Z – Parked document which was deleted.

C. No. of ways to trace the deleted Parked document: - You can able to trace the details of the deleted parked document either t codes or tables total in 5 ways.

C.1. FBV5 - Document Changes of Parked Document: - This FBV5 transaction will allow the user to view the changes in a parked document. The user ID of the individual making the change, date of the change and time of the change can also be viewed. Please enter the company code, document number, Fiscal year and from change date. If you know the changed date exactly so please inputs that date else give probable date.

In the below given screen I have given the changed date as 09/26/2013 (MM/DD/YYY) else give like probable date as 08/01/2013.

Click ENTER

And then please select the selected field and then click Choose button

Then the following pop-up will appear.

Click first item in the above as selected below.

Then the following pop- up will appear – It will show the details like date of deletion of parked document, user name that was deleted this document and parked document no.

You may select a line item and just double click on it to get the detail of the change. Then the following screen will appear which contains the details like date of deletion of parked doc., time of deletion, user name who got deleted this parked doc. as highlighted below.

The user id is defaulted for auditing purposes. To fix the responsibility of the user who got deleted this parked document.

Click to close the detail screen and return to the previous screen. Click the second line item.

Click Technical names on icon then this pop- up will appear which contains the technical table details which captures this data. You can able to track this technical information like VBKPF and VBSEG tables details in CDHDR & CDPOS Tables also.

Then the following pop - up will appear – It will show the date of deletion of parked document, user name who was deleted this document and document no.

Click or press ‘Shift+F3’. You have completed this transaction successfully.

Note: - But parked documents deleted are physically deleted in table VBKPF. As a consequence with deletion of the preliminary posted doc is physically deleted in the table VBKPF so it is not displayed.

I am explaining the balance 4 ways in my next blog Part-II. Because I dont want to put too much information on this blog.By keeping an eye on readers point of view, i am continuing this concept in the next blog.

Here is Part-II

http://scn.sap.com/docs/DOC-48772

As a first step to SCN i am contributing this document from my end.I am requesting you all to read this blog and provide your valuable feed back along with the rating.

Thanks & Regards,

Lakshmi S

Lockbox process

The predominant way payments are made in US is by checks. Lockboxs help in speedy deposit of funds and clearance of customer accounts. Lockboxs are special depository accounts set up at a bank to which customer remit their invoice payments.

Banks daily than submit company’s an electronic file listing all deposits and invoices that are paid against. Company’s than upload these files in SAP and update their balance and clear customers i.e. A/R accounts.

Some company’s setup single lockbox whereas others set up lockboxs at different locations thought the country in order to decrease the time it takes to receive the customer payments.

     Figure 1: Lockbox Process Flow

Lockbox File Formats

SAP supports both US lockbox file formats – BAI & BAI2.Each bank has its own standard BAI and BAI2, hence configuration and testing needs to be done depending on bank file configuration.

Hence if you are not comfortable with bank file format either you can approach them to modify it depending on your requirement else ABAP can help in writing a preprocessing program and make file fit with SAP standard format.

Difference between BAI and BAI2

BAI2 is advised as because it has greater probability of producing automatic matches in the processing and because it allows one to record deduction information and create proper residual postings.

Relationship between EBS and Lockbox

Assume on Day 1 company receives Lockbox file from bank and on Day 2 receives EBS file.

Day 1 When the bank receives a check from customer with remittance information its sends it in Lockbox file. Lockbox file when processed will generate below accounting posting

          Dr Bank Clearing account - incoming

     Cr Lockbox Clearing Account

          Dr Lock box clearing account

     Cr Customer account (customer sub ledger)

Day 2 when the check is cleared in bank, it appears in EBS. EBS when processed produces below accounting entry

Dr Bank Main GL

          Cr Bank Clearing Account - incoming

Lockbox Configuration

House Bank Configuration

Create House banks

1. Menu Path: Financial Accounting à General Ledger Accounting à Bank – Related Accounting à Bank Accounts à Define House Banks

Transaction Code: FI12

Under the house bank create Bank account from FBZP transaction code.

After creation of House bank and Bank account under company code, it should look like this in FBZP transaction code.

Lock Box Configuration

1. Path: IMG à Financial Accountingà Bank Accounting à Business Transactions à Payment Transactions à Lock box àDefine posting parameters

T Code: OBAX

Select highlighted row and click on change item button.

Document Number Length: Field is only applicable for BAI record

1. Num. of doc numbers in type 6: Field is only applicable for BAI record
2. Num. of doc numbers in type 4: Field is only applicable for BAI record

G/L account Postings: Activate this indicator to make postings to your cash account in the G/L for deposits. Activating this field is recommended

Incoming Customer payments: Activate this indicator to make postings to A/R sub ledger in order to clear customer accounts and create residual postings. Activating this field is recommended

Insert Bank Details: Applicable for batch input session name that updates bank details of master records for customers who have either changed bank information or did not have bank information maintained for them

G/L account posting type

1 - Creates posting to G/L account for every check in the file     

2 - Creates one posting to the G/L account for entire lockbox file

3 - Creates one posting to the G/L account for entire batch

Automatic Posting from lockbox        

1. IMG à Financial Accountingà Bank Accounting àBusiness Transactions àPayment Transactionsà Lock boxà Define posting data

OBAY

Destination: This field should contain the destination code the bank submits to you in your lockbox file

Origin: This field should contain the your lockbox number (bank account) number at the bank

IMG à Financial Accountingà Bank Accounting àBank Accounts à Define Lockboxes for House bank

Click on first option

Customer Master Data

Transaction Code: XD03

Maintain Bank details in customer master data which bank will send in lockbox file

.

Customer Invoice Posting

Post one 600 amount customer invoice. Invoice will display in open state.

T code FB70

Open the invoice

Transaction code: FB03

T code: FBL5N (Customer Report)

Below report shows customer item and it’s not cleared.

Lockbox file processing

SAP gives option of using one of the two standard algorithms for lockbox processing. A common misrepresentation is that one can create own algorithm which is not correct. We can only use the pen delivered by SAP. Program RFEBLB00 is the processing program. Documentation can be viewed for this program from SE38 transaction code. This program contains lot many user exits whether one can add any additional business logic.

Two algorithms that are used are 001 and 003. If file contains checks that cannot be applied against specific invoice but for which customer account is known, SAP posts them on the customer account without reference to any specific invoice. Using algorithm 003, SAP distributes the check across open invoices, beginning at the oldest invoice and working its way forward until the check amount is fully distributed.

File Import:

1. Menu Path: SAP Easy Access à Accounting àFinancial Accounting àBanks  à Lockbox à FLB2 Import.

Transaction Code: FLB2

Save the lockbox file attached with this document and modify the document number in file with open customer invoice.

Click on green execute button.

Click on back button.

Transaction Code: FLB1

Enter Lockbox details and click on execute button

Select the one which contains data in file. For example if file contains 1123456 is second session name will be 1123456. Right click on 1123456 and select Process Checks options.

Right click on Session name and click on Process option.

Vendor Document Clearing Report

Again view customer invoice it will be displayed as cleared from the payment received and posted via lockbox

Notes

1)   If you get below message, modify the following in file. Unique key for each lockbox file is its header record i.e. Destination, Origin name, Date and time. Modify the seconds’ part and rerun the file.

1)   Sap file generation

            Use Test Lockbox Generation Programs RFEBLBT2 to generate BA12 format and RFEBLBT3 for IDOC format. These programs will generate customer open items and a lockbox file for processing.  Utilize program RFEBKA96 to delete loaded test data

2)   Sample File Understanding

100MANGDESTINMANGORIGIN130903123557

20000000000000000000000

56660011123557130903MANGDESTINMANGORIGIN

666600200000600000110003900345205865100000002

466600360191800000023   00000000600000000000

766600411235571309030010000060000

8666005112355713090300010000060000

9000000

File content explanation with help of differnet Color Codes

100000002 =Check Number

666 = Batch ID

1800000023 = FI customer Invoice

123557130903 = Date & time in Header (i.e. first record) and Time & Date in below records.

600000 = Check/Invoice Amount depending on Row

110003900345205865 = Customer Master Record Bank details.

3)   Sample file of BAI2 program can also be generated from SAP directly on execution of programs

Same can be downloaded and uploaded with just modification of document number else copy from below location

100MANGDESTINMANGORIGIN130903123557

20000000000000000000000

56660011123557130903MANGDESTINMANGORIGIN

666600200000600000110003900345205865100000002

466600360191800000023   00000000600000000000

766600411235571309030010000060000

8666005112355713090300010000060000

9000000

The scripts are difficult to customize and therefore its easy to develop new PDF based forms to generate customer account statements.

Below are a few quick steps to configure the adobe forms for generating customer account statemetns

.

Go to IMG>Financial Accounting (New) > Accounts Receivable and Accounts Payable >Vendor Accounts >Line Items >Correspondence> Make and Check Settings for Correspondence

1. Define correspondence type
   1. Copy standard correspondence type SAP06 to a new correspondence type ZPDF06
   2. Change settings if required
   3. Click on save and then exit step
2. Create Report Variants for Correspondence
   1. Create a variant for program RFKORD10_PDF with name ZPDF06
   2. The variant ZPDF06 of RFKORD10_PDF should be same as variant SAP06 for program RFKORD10 and/or make the necessary settings for the variant
   3. Click Save and then exit step
3. Assign Programs for Correspondence Types
   1. Create a new entry in the node
   2. Enter Company Code (Optional) and correspondence type (ZPDF06, in this case)
   3. Set Name of the print program as RFKORD10_PDF
   4. Set name of the variant as ZPDF06 (or the one created in step 2)
   5. Click on save and then exit the step
4. Define Sender Details for Correspondence Form
   1. Copy entry for company code = blank and program = RFKORD10 to create a new entry with company code (Optional) and program = RFKORD10_PDF
   2. Click on save and then exit the step
5. Go to transaction SM30 enter view name as V_T001F2 and click on maintain
   1. Create new entry in the view
   2. Enter Company code (Optional), Enter program name as RFKORD10_PDF
   3. Enter form mane as F140_ACC_STAT_01 or the Z-adobe fo
      Please note that the interface for Z-adobe form should be exactly same as that of  adobe form F140_ACC_STAT_01
   4. Click on save and then exit the step
6. Execute transaction F.27 for the correspondence type created in steps above

Lots of time when we clearing we want to use field in F-03 other transaction we need common field to clear the item but that field is not available F-03. Like now we want to do clearing on the Basis Trading Part.BA which not available in F-03

Now we will add Trading Partner Business Area field.

Go to Transaction - O7F1.

Now choose the position where you want to enter and select that field. Here I will enter After Assignment field so I am selecting Assignment field and clicking on Insert after

Now you can choose the field you want to display like Trading Partner business area by clicking on standard field.

Now double click on file you want enter

Now save.

PS: If you are doing this change in development client then system will prompt with transport request to move in different Environment.

Now go to F-03 and choose any GL account and then click on Other

Press ENTER and Pop of other selection will come

Now as you see New filed for Selection after assignment Field.

I hope this will help you and all suggestions are welcome.

Many Thanks

Regards

Preeti Agarwal

Hi ,

I have seen lot of post About  Profit centre Distribution cycle definition where we can see Cost centers instead of Profit centre .

I hope below document will help you .

Configuration changes  for Profit centre distribution

SPRO – IMG Implementation –FINANCIAL Accounting (NEW)-General ledger Accounting –Period Processing –Allocation – defined field’s usage for distribution

                       Or

Direct T-code – GCA6

Will give you below screen

Now choose Cost Center ( Actual )  and double click on that (This will give you current settings)

Now delete all setting in here ( in change mode )and should look like as below (BELOW IS SAND BOX SCREEN )

And SAVE the above changes  And now go back to screen and choose profit centre to Make sure that when you create Cycle you can see PROFIT CENTER there .

After this DEFINE your DISTRIBUTION CYCLE in FAGLGA31   same as Usual. You won’t find any cost centre field here this time.

Now you can see the You do not have any Cost centre . All You see is just Profit Center.

SAVE this cycle and run  Profit Centre distribution Via T-code FAGLGA35 .

Please assign the point if you think its helpful.

A Validation / Sustitution is transported to the Traget System using T. codes GCT9 and GCT0 respectively. For the same, you select Validation / Substitution in the Dropdown list in these t. codes and include it in a Transport request.

However, once a Validation / Substitution is deleted from the System, the same do not appear in the Dropdown list and thus not available for inclusion in the Transport request,

This document aims at inclusion of an already deleted Validation / Substitution in a Transport request and then Transport it to a Target System.

Scenario:

You have created a Validation / Sustituion and moved it to Quality / Production System. However, later on it was realised that the same is either not required or created wrongly and thus Need to be delted in all Systems.

Validation Overview in Development System:

Validation Overview in Quality System:

As can be seen, the Validation Z10003 has been deleted in the Development System after it was Transported to the Quality System.

Inclusion of Deleted Validation in the Transport Request

T. Code: GCT9

Doing the F4 on the Validation Name field, the deleted Validation do not appear in the Dropdown list.

So, rather than doing a F4 on the field, enter the Deleted Validation manually in the Box.

Then, go to Object and select the Option " Delete in Target Sytsem" (as shown below)

A message will appear

Press "Enter". The System will prompt for a Transport request.

Enter the "Workbench Transport Request" and then Transport it to the Target sytsem as per the deifned process in your organization.

For Substitutions, the Process is exactly the same. You just Need to use T. Code GCT0 (instead of GCT9)

There is also a possibility to remove an already added Validation / Substitution from a Transport request using the same T. codes.

Scenario: You have included multiple Validations / Substitutions in a Transport request, however, later you do not want to Transport a particular Validation / Substitution and hence want to delete from the Transport request.

It will Prompt for the Workbench Request from which you want to delete the Validation / Substitution. Enter the desired Transport request.

This project is working for providing support to IS- SAP Team. This project provides support to all organizations functions i.e. Billing, Tax, Finance etc. Author belongs to SAP FI support team and it provides support to finance users. All existing finance processes are being supported by team. Most of SAP FI modules like GL, AP, AR, Asset, Fund management, Treasury, banking are being supported by team. SAP FI support team dedicatedly works in order to provide smooth functioning of finance department. An extended support is provided during month and quarter ends apart from normal support work.

Introduction: This is to understand and to learn how to add Brazil postal codes to the standard SAP system in order to pay account payables invoices which carry Taxes line items.  As every county has a different rate of tax and different counties pay different kinds of taxes, hence it becomes necessary for SAP to know from which region the business transactions originates and the region which deals or purchases the goods or services. We will delve into jurisdiction code which is a code used for determining tax rates in Brazil; it controls which tax authorities must be paid for any particular transaction.

The tax jurisdiction code is comprised of the following two parts, the tax region and municipal region, the Tax region comprises of 1 to 3 characters while the municipal region, which comprises of 4 to 16 characters.

Procedure:

Procedure is to add Brazil postal codes a procedure for a country version. You need to configure this as this supports Vertex tax calculation procedure and enables payment of invoices.

Assumptions:

Tax configurations in following T. codes:

• OBBG
• OBCO
• OBCP
• FTXP
• OBCL

Have already been set up.

Configuration:

We need to configure following settings: -

• Please Check whether the given postal codes were available in production systems, generally the postal codes won't be available, Some times couple of codes will be available with other Jurisdiction codes.

• Ensure the user/business has provided the following information:

• Region
• From post code
• To post code
• Jurisdiction code

Please note: the text field will populate by itself.

• Please add the given postal codes in development systems by following the below path.

• We can add the postal codes directly in the table " J_1BTREG_CITYV". We can add the postal codes through -> SE16 -> table name. Please be informed this is not the correct process. We have to add through the path mentioned above.

• Incase of any ambiguity on the city of a particular postal code, Please check the below link for clarification.

http://www.correios.com.br/eng/sys/cep/default.cfm

• Please enter the postal code, and click on search, it will display the city name which is associated with that postal code. This can be cross-verified with the data available in our SAP system. Incase of deviations please get it clarified with user.

• Use country key: br
• Define Tax Jurisdiction Codes

• Here define the jurisdiction code as per the country key..
• Next assign the postal codes
• Please view the below screen shot and click on the tab – ‘New entries’

Post this, Add the following:

• Region
• From post code
• To post code
• Jurisdiction code

• And hit the enter button after each line.
• After adding all the lines, click on the save button and create a transport request as per the convention followed by the customer’s standards.
• Request Basis team to move configuration transport request to all test systems.
• Test the data in Integration systems and Quality systems
• Procure UAT after sending screen shots from test systems
• Once you receive the UAT create a change request
• Post implementation, send screen shots to the user and ask for closure of the ticket.

Check is one of the important payment methods for the business to pay for all the vendors for regular day to day business transactions.

Check inventory is under the control of Finance and accounts payable department.

Business can use the payment document number as a check number.  But if the business wants to use the different number ranges other than the payment document number then it is possible by using the Check management method.

Bank defines number intervals and based on that business defines their own number intervals

The document explains , If the  check number not triggered in Reference key , what are the inital checks to do and how to execute transaction FCHN or Program RFCHKU00 to update the check number in target field Reference key.

In the below example ,check form have three windows . First window is the original check which we submitted to bank renaming two are counter copies for filing purpose .

Total amount on the check will be triggered from table REGUH - RWBTR (First window). Break of that total line items will be displayed in  second window from table REGUP -WRBTR  in case any cash discount given then WRBTR - WSKTO. Thrid window will be the same as second.

We have to do our own customization by using Standard check printing form F110_PRENUM_CHCK and Program RFFOUS_C are available in SAP for print check.

Example of Test case explained step by step:

1 Executing FBL1N and selecting vendor line items which to be paid by check and updating with payment method filed with C

2 In F110 for program RFCHKU00 variant maintained to updated the check number in target field “Reference”

3 Payment run executed successfully.

4 In clearing document at Reference field check number not updated.

5 for this check PAYR table (check register FHCN), REGUH and REGUP tables, Check lots FCHI and Standard check printing form F110_PRENUM_CHCK and Program RFFOUS_C are available in SAP.

6 To update check execute FCHN transaction by giving inputs like payment run, payment document etc.

7 After execution some documents still not updated check number in reference, in this we have to check the customized program. Once customized program rectified.

You need to delete the steps in the reverse order

Firstly you need to delete output and edit payments –delete output

Reverse the payment run and proposal run

Re execute payment run and then payment run

Now check PAYR

8 For check print use transaction code FBZ5

9 Once check enhance at bank, update the enhancement date in transaction code FCH6

Step 1 :

Selecting all vendor line items updating payment method C through transaction code FBL1N

Press F5 Key and Press Cnt+Shift+F9 for mass changes

Now refresh data payment method C updated

Before execution of F110 , check the check register last check issued.

During F110 execution parameter for payment method C (Check issue)

/ZRFFOUS_C

RFCHKU00

Variant maintained for /ZRFFOUS_C

Variant maintained for RFCHKU00

Payment run executed successfully

Details also updted in log

See the clearing document in document list  check number not triggered  in reference key field.

Now data in tables ,  REGUH and REGUP  and PAYR (FCHN) tables.

Check register check check 101575 generated, but in check lot last check of showing 101574 only.

To update the check number in check lot as well as in reference field execute FCHU

Now execute the program  RFCHKU00 (SE38)  or FCHU Transaction code . Give the inputs of next check number and payment document .

Check the document list now.

For the rest of documents not updated , reason as our own customized check  form dimension print  restricted line up to 7 in second and third window.

Check Print FBZ5

Check Form

Some of the Transcation related check

Thanks to all for going through my document. Please provide your valuable suggestion and rating.

If any thing i have missing ,please share to all it will help us.

e share the information to all it will help.

                  How to add Custom Message to SAP Log On screen

Scenario:

Adding custom message / text to SAP Log on screen.

Step 1:

Go to Transaction Code SE61

Step 2:

Once you execute T.code SE61, on next screen in

• “Settings” area select “General Text” against “Document Class”
• Language “English”
• In “Document” section enter “ZLOGIN_SCREEN_INFO”.

       And click on “Create” button.

Step3:

On next screen – Enter desired info e.g.

“For any SAP related queries please contact: sapbasis@xys.com”

Step 4:

After entering desired message click on “Save” button and “Activate” the message via clicking on “Activate” button (Light Candle). Message has been "Activated" confirmation message will be displayed at bottom of the screen.

Step 5:

Once performed all above said activities please log off from  SAP and log in again, changes are taken place and message maintained can be seen on main screen.

This document explains about the code page issue in the DME file while the file is generated to the application
server and when there is a Unicode is active in the ECC System.

Hello, SAPers!

          Sometimes when you create custom DMEE tree to meet the requirements of your house bank concerning the format of file with payment orders, you have to configure the field with counter of line items in file. This counter represents a simple field with incremental value from 1 to n, where n equals the number of line items in the payment run. However, there are no standard field in the structures FPAYH, FPAYHX and FPAYP. Therefore you have to use another standard functionality that will be discussed in this document.

          In order to create node that will retrieve the consequential number of line item in the payment run the following activities have to be performed:

          1) Create technical node

          Technical node stores values that are used in other tree nodes (elements or atom) by a reference to this node. However, the values stored in technical nodes are not shown as output in a target file. Thus, you have to create a technical node with the following characteristics:

          On the tab Source specify the constant value that equals to 1:

          2) Create element with reference to tree node with the following characteristics:

          On the tab Source specify the reference to the technical tree node created previously and insert "3" (Counter reading) in the field Attribute:

          The nodes in the tree menu of DMEE structure for your payment medium should look as follows:

          Create other nodes as required for payment medium for your bank and activate the tree. Afterwards, when you run the transaction FBPM and create the payment medium, your will have the counter starting at one in the beginning of each line item:

          I hope this information will be useful. All suggestions are welcome!

     Best regards,

     The Wirtschaftsmann