Explore topic-wise InterviewSolutions in .

User exits are SAP supplied ‘hooks’ within specific program which allow user customizations to meet specific REQUIREMENTS.

When the program is run, SAP checks to see if the user has setup any logic within these hooks.

For example in the fixed ASSET module lets say the gain/loss from disposal is normally booked to GL account 65410. During posting however you wish to book certain asset retirement transaction types to 65499 for reporting purposes. An enhancement AINT0002 exists to do this.

User exits are commonly used also with validation and substitution rules.

To implement user exist you need an understanding of the ABAP programming language. However for those who have worked ACROSS several SAP PROJECTS its inevitable that at some point they will have come across user exits at some STAGE even if its just at a conceptual level.

User exits are SAP supplied ‘hooks’ within specific program which allow user customizations to meet specific requirements.

When the program is run, SAP checks to see if the user has setup any logic within these hooks.

For example in the fixed asset module lets say the gain/loss from disposal is normally booked to GL account 65410. During posting however you wish to book certain asset retirement transaction types to 65499 for reporting purposes. An enhancement AINT0002 exists to do this.

User exits are commonly used also with validation and substitution rules.

To implement user exist you need an understanding of the ABAP programming language. However for those who have worked across several SAP projects its inevitable that at some point they will have come across user exits at some stage even if its just at a conceptual level.

The report painter is a pre-delivered SAP REPORTING tool for the controlling MODULE. It allows SAP reports to be quickly created, typically actual VERSUS plan analysis for cost ELEMENTS, internal ORDERS and cost centers.

The report painter is a pre-delivered SAP reporting tool for the controlling module. It allows SAP reports to be quickly created, typically actual versus plan analysis for cost elements, internal orders and cost centers.

LSMW is a technical tool used for MIGRATING master data and transaction data from your OLD ‘legacy’ systems to SAP.

Though usually setup by your ABAP programming colleagues, the LSMW projects are usually run by FI/CO project TEAM members in ORDER to upload vendors, customers, COST centers, internal orders etc.

LSMW is a technical tool used for migrating master data and transaction data from your old ‘legacy’ systems to SAP.

Though usually setup by your ABAP programming colleagues, the LSMW projects are usually run by FI/CO project team members in order to upload vendors, customers, cost centers, internal orders etc.

COEP is the CO object line ITEM table.

CSKA is the cost ELEMENT master table (dependant on chart of accounts).

CE1xxxx (where xxxx is the NAME of your operating concern) is the profitability analysis line item table.

COEP is the CO object line item table.

CSKA is the cost element master table (dependant on chart of accounts).

CE1xxxx (where xxxx is the name of your operating concern) is the profitability analysis line item table.

BKPF is the DOCUMENT header table. It stores all the fields COMMON to all of the document line items such as posting date, currency key, document number etc.

BSEG is the associated line item table to BKPF. Specific line item information such as posting key, GL account, document amount are stored.

GLT0 is the SUMMARIZED account balances table SHOWING account balances by period, by account, by fiscal YEAR.

BKPF is the document header table. It stores all the fields common to all of the document line items such as posting date, currency key, document number etc.

BSEG is the associated line item table to BKPF. Specific line item information such as posting key, GL account, document amount are stored.

GLT0 is the summarized account balances table showing account balances by period, by account, by fiscal year.

The SPL is a user defined ledger which can be built to support reporting requirements which cannot normally be met through the usual SAP modules.

You can pull information from MANY SAP modules such as FI, CO, MM, SD and build user defined fields whose contents are BASED on calculations from other SAP standard information.

Typical uses include:-

•  Reporting using an alternative fiscal year variant other than the one assigned to the entity.
• Reporting in a different currency (maybe to meet a NEW head OFFICE reporting currency).
•  Meeting USGaap and local reporting requirements.

The SPL is a user defined ledger which can be built to support reporting requirements which cannot normally be met through the usual SAP modules.

You can pull information from many SAP modules such as FI, CO, MM, SD and build user defined fields whose contents are based on calculations from other SAP standard information.

Typical uses include:-

Using SAP transaction GCU1, FI DATA can be TRANSFERRED for a particular company code, fiscal year or SPECIFIC document NUMBER RANGE.

A similar transaction exists for controlling data, GCU3.

Using SAP transaction GCU1, FI data can be transferred for a particular company code, fiscal year or specific document number range.

A similar transaction exists for controlling data, GCU3.

Commitment line ITEMS in CO are not actual cost items but rather committed expenditure items GENERATED through purchase ORDERS.

Commitment line items in CO are not actual cost items but rather committed expenditure items generated through purchase orders.

A company code REPRESENTS a specific legal entity for financial reporting PURPOSES and represents the lowest level at which external financial accounts can be produced.

It’s the main organizational object in the FI module and is assigned to a CONTROLLING area in CO. One company code MAY only be assigned to a single controlling area. (A controlling area may have multiple company CODES assigned to it).

A company code represents a specific legal entity for financial reporting purposes and represents the lowest level at which external financial accounts can be produced.

It’s the main organizational object in the FI module and is assigned to a controlling area in CO. One company code may only be assigned to a single controlling area. (A controlling area may have multiple company codes assigned to it).

This is the main company code configuration table and includes such ASSIGNMENTS as:-

•  Fiscal YEAR variant.
• Company assignment.
•  Local currency SETTING.
•  Credit control area.

This is the main company code configuration table and includes such assignments as:-

Using transaction code EC01, the most straightforward way of creating a new company code is to copy an existing VALUE.

All ASSOCIATED data such as the fiscal year variant and assignments to CONTROLLING AREA and credit control area are TAKEN across from the source value.

Transactional data of course is not copied. Here, interviewers are simply looking to hear the word “copy” to prove that you have defined a SAP FI/CO organizational structure before.

Using transaction code EC01, the most straightforward way of creating a new company code is to copy an existing value.

All associated data such as the fiscal year variant and assignments to controlling area and credit control area are taken across from the source value.

Transactional data of course is not copied. Here, interviewers are simply looking to hear the word “copy” to prove that you have defined a SAP FI/CO organizational structure before.

Financial statement versions FSV’s are the structures FORMING the P’L and Balance sheet reports from the FI module.

Accounts are assigned to the end nodes in the reporting STRUCTURE tree. DEPENDING on the setup debit /credit balances can be reflected in DIFFERENT asset / liability columns where required.

Financial statement versions FSV’s are the structures forming the P’L and Balance sheet reports from the FI module.

Accounts are assigned to the end nodes in the reporting structure tree. Depending on the setup debit /credit balances can be reflected in different asset / liability columns where required.

The company code is the LEGAL entity organization unit and the lowest LEVEL at which external financial statements are PREPARED.

The company id is a HIGHER organization unit used for consolidation in the SAP system. A single company id can have many company codes assigned to it so long as the fiscal YEAR variant and chart of accounts is consistent.

The company code is the legal entity organization unit and the lowest level at which external financial statements are prepared.

The company id is a higher organization unit used for consolidation in the SAP system. A single company id can have many company codes assigned to it so long as the fiscal year variant and chart of accounts is consistent.

AuC’s can be used to track investment cost during projects or asset assembly. Following COMPLETION their costs can be settled to other FIXED assets or to other CO cost objects such as real internal orders or cost centres.

For EXAMPLE, the construction of a new BUILDING, the various costs involved (engineering, utlity cost etc) could be collected under an AUC, before being settled to an asset under the 'buildings’ asset class at the end of the project.

AuC’s generally are not DEPRECIATED until completion.

AuC’s can be used to track investment cost during projects or asset assembly. Following completion their costs can be settled to other fixed assets or to other CO cost objects such as real internal orders or cost centres.

For example, the construction of a new building, the various costs involved (engineering, utlity cost etc) could be collected under an AUC, before being settled to an asset under the 'buildings’ asset class at the end of the project.

AuC’s generally are not depreciated until completion.

There are many ways of booking APC to fixed ASSET RECORDS including:-

•  Via F-90 – Acquisition with Vendor.
• ABZON – Acquisition with AUTOMATIC offsetting entry.
• ABZP – from affiliated company.
• From settlement of an asset under construction (AIBU).
• From goods RECEIPT (or invoice receipt depending on system setup) relating to a purchase order.

There are many ways of booking APC to fixed asset records including:-

Normally you cannot POST direct to reconciliation accounts. However there is a configuration TRANSACTION OAK5/ OAMK which can be used to TEMPORARILY remove the reconciliation flags to allow the BALANCES to be journaled onto the fixed asset reconciliation accounts.

Normally you cannot post direct to reconciliation accounts. However there is a configuration transaction OAK5/ OAMK which can be used to temporarily remove the reconciliation flags to allow the balances to be journaled onto the fixed asset reconciliation accounts.

SKF’s are statistical (or information values) used in cost allocations such as ASSESSMENTS and distributions.

For example we may have an SKF for ‘head COUNT per department’. When utility costs are allocated across various departments we could PERFORM the percentage allocation based on the ‘head count’ SKF.

SKF’s are statistical (or information values) used in cost allocations such as assessments and distributions.

For example we may have an SKF for ‘head count per department’. When utility costs are allocated across various departments we could perform the percentage allocation based on the ‘head count’ SKF.

The reconciliation ledger effectively highlights differences by account across the FI and CO modules. A report is PRODUCED by the RL program, identifying where transactions have been BOOKED across entities in controlling that WOULD impact the EXTERNAL reporting produced from the FI module.

The RL program can then EITHER post automatic corrections or you can choose to post manual corrections based on the information in the RL report.

The reconciliation ledger effectively highlights differences by account across the FI and CO modules. A report is produced by the RL program, identifying where transactions have been booked across entities in controlling that would impact the external reporting produced from the FI module.

The RL program can then either post automatic corrections or you can choose to post manual corrections based on the information in the RL report.

The FOLLOWING settings are made during the configuration of ORDER types (transaction KOT2_OPA)

•  Number ranges assigned to the order master on creation.
• Planning and budgeting PROFILES.
•  STATUS profiles.
•  Order layouts.

The following settings are made during the configuration of order types (transaction KOT2_OPA)

Sometimes COPA reporting performance is severely affected by poor INITIAL setup. Anyone involved in a full COPA PROJECT lifecycle in a retail or manufacturing environment will have come across such issues hence the reason the interviewer is asking the QUESTION. The most IMPORTANT thing.

Sometimes COPA reporting performance is severely affected by poor initial setup. Anyone involved in a full COPA project lifecycle in a retail or manufacturing environment will have come across such issues hence the reason the interviewer is asking the question. The most important thing.

The OPERATING concern is the MAIN organizational UNIT in Profitability Analysis. It’s structure depends on the configuration setup of CHARACTERISTICS and value fields.

It is assigned to a CONTROLLING area on a one to may basis i.e. one controlling area may be assigned to only one operating concern, one operating concern can be assigned to many controlling areas.

The operating concern is the main organizational unit in Profitability Analysis. It’s structure depends on the configuration setup of characteristics and value fields.

It is assigned to a controlling area on a one to may basis i.e. one controlling area may be assigned to only one operating concern, one operating concern can be assigned to many controlling areas.

This is an incredibly popular QUESTION for any positions with a COPA component.

The interviewer will be looking for some of the following:-

• AB can easily be reconciled with FI at account level through the USE of cost elements. CB can only be reconciled at account group level (such as revenues, sales deductions etc) as values are stored in “value fields” as OPPOSED to accounts.
•  In CB data is stored by posting periods and weeks. In AB storage is only by periods.
•  In CB transactions can be stored in operating CONCERN currency and company code currency. In AB transactions are stored in controlling AREA currency, company code currency and transaction currency.
• In CB you can create cross controlling area evaluations or cross controlling area plans. In AB you cannot as the chart of accounts may differ.
• In CB the cost of good sales (COGS) are updated via material price valuations. Stock change values can be transferred to CB COPA during billing. Timing differences can occur if the goods issue and billing documents are in different posting periods. In AB the value posted in the stock change is posted simultaneously to COPA.

This is an incredibly popular question for any positions with a COPA component.

The interviewer will be looking for some of the following:-

CHARACTERISTICS are ANALYTICAL information fields used in CO-PA. TYPICAL EXAMPLES include customer number, brand, distribution channel etc.

Characteristics are analytical information fields used in CO-PA. Typical examples include customer number, brand, distribution channel etc.

VALUE fields are number/value related fields in PROFITABILITY ANALYSIS such as quantity, sales revenue, discount value etc.

Value fields are number/value related fields in profitability analysis such as quantity, sales revenue, discount value etc.

AAM’s are blocks of document line items that can be used repeatedly to prevent MANUAL re-entry.

Which FIELDS are included in the AAM LAYOUT can be CONFIGURED using O7E3.

AAM’s are blocks of document line items that can be used repeatedly to prevent manual re-entry.

Which fields are included in the AAM layout can be configured using O7E3.

An existing asset can be scrapped (transaction ABAVN), TRANSFERRED to another company CODE (ABUMN), SOLD to a customer account in the accounts receivable MODULE (F-92), sold with revenue but the revenue is BOOKED to a GL account (ABAON).

An existing asset can be scrapped (transaction ABAVN), transferred to another company code (ABUMN), sold to a customer account in the accounts receivable module (F-92), sold with revenue but the revenue is booked to a GL account (ABAON).

Over TIME the local currency equivalent of foreign currency amounts will fluctuate according to exchange rate movements. Usually at month end, there is a requirement to restate these amounts using the prevailing month end exchange rates.

SAP can revalue foreign currency GL account balances as well as outstanding customer and vendor open item balances.

In SAP configuration, you define the balance sheet adjustment account and which accounts the realized gain/loss should be BOOKED.

A BATCH input session is created to AUTOMATICALLY post the required ADJUSTMENTS.

Over time the local currency equivalent of foreign currency amounts will fluctuate according to exchange rate movements. Usually at month end, there is a requirement to restate these amounts using the prevailing month end exchange rates.

SAP can revalue foreign currency GL account balances as well as outstanding customer and vendor open item balances.

In SAP configuration, you define the balance sheet adjustment account and which accounts the realized gain/loss should be booked.

A batch input session is created to automatically post the required adjustments.

Recurring entries (SETUP in FBD1 ) can eliminate the NEED for the manual posting of accounting DOCUMENTS which do not change from MONTH to month.

Recurring entries (setup in FBD1 ) can eliminate the need for the manual posting of accounting documents which do not change from month to month.

When you define the fiscal YEAR VARIANT you can choose to define ADDITIONAL special periods. These can be used for example for the posting of year end adjustments, auditors adjustments etc.

Periods 1-12 can be closed and periods 13-16 left OPEN during year end closing.

When you define the fiscal year variant you can choose to define additional special periods. These can be used for example for the posting of year end adjustments, auditors adjustments etc.

Periods 1-12 can be closed and periods 13-16 left open during year end closing.

Fiscal year variants (FSV’s) are assigned to a company CODE via transaction OBY6. They determine the FINANCIAL reporting periods of an entity e.g. 13 4-weekly periods, calendar months, 5-5-4 reporting etc.

During MONTH end the current fiscal reporting period will be and the next month opened. Its possible to open and close specific ledgers e.g. AP, AR, GL and EVEN sets of accounts within those ledgers. This way its possible to, for example, close all GL accounts and LEAVE only the month end adjustment accounts open for posting.

Fiscal year variants (FSV’s) are assigned to a company code via transaction OBY6. They determine the financial reporting periods of an entity e.g. 13 4-weekly periods, calendar months, 5-5-4 reporting etc.

During month end the current fiscal reporting period will be and the next month opened. Its possible to open and close specific ledgers e.g. AP, AR, GL and even sets of accounts within those ledgers. This way its possible to, for example, close all GL accounts and leave only the month end adjustment accounts open for posting.

Sort keys are stored in customer, VENDOR and GL master records. They DETERMINE what value is populated in the ‘assignment’ field in the document line ITEMS posted.

There are several standard entries in a pre-delivered SAP system and additional entries can be CONFIGURED if required.

A very common use for sort key 014 Purchase Order number for EXAMPLE, is to allow the GR/IR clearing GL account to be cleared automatically.

For FI/CO jobs in a logistics environment this is a common question.

Sort keys are stored in customer, vendor and GL master records. They determine what value is populated in the ‘assignment’ field in the document line items posted.

There are several standard entries in a pre-delivered SAP system and additional entries can be configured if required.

A very common use for sort key 014 Purchase Order number for example, is to allow the GR/IR clearing GL account to be cleared automatically.

For FI/CO jobs in a logistics environment this is a common question.

There are TWO screens which have to be maintained for each new GL account. The first is at ‘chart of account’ level (transaction FSP0) and contains the information used by all company codes USING this chart of accounts such as description, group account NUMBER etc.

Each company code using this chart will then add its own company code VIEW (via transaction code FSS0) which contains localized data specific to that entity e.g. field STATUS group, alternative account number etc.

The chart of accounts screen must be maintained before the local company code screens.

There are two screens which have to be maintained for each new GL account. The first is at ‘chart of account’ level (transaction FSP0) and contains the information used by all company codes using this chart of accounts such as description, group account number etc.

Each company code using this chart will then add its own company code view (via transaction code FSS0) which contains localized data specific to that entity e.g. field status group, alternative account number etc.

The chart of accounts screen must be maintained before the local company code screens.

At year end P&L accounts are cleared down to the retained earnings balance sheet account. This field contains an INDICATOR which is linked (in the IMG TRANSACTION OB53) to the specific GL account use in this CLEAR down.

At year end P&L accounts are cleared down to the retained earnings balance sheet account. This field contains an indicator which is linked (in the IMG transaction OB53) to the specific GL account use in this clear down.

Validation rules (CONFIGURED via transaction OB28) enforce certain conditions when FI POSTINGS are MADE.

Validation rules comprise:-

• A prerequisite event that has to occur for the validation check to TAKE place.
• The check itself.
• The OUTPUT message that is to be displayed (you can choose between a warning or error message).

Validation rules (configured via transaction OB28) enforce certain conditions when FI postings are made.

Validation rules comprise:-

The exchange rate can be entered via either:-

• Directly on the document HEADER.
• Derived from the exchange rate table (by leaving exchange rate blank).
• INDIRECTLY, by entering the EXPLICIT local currency amount so the SYSTEM is forced to use a specific exchange rate.

The exchange rate can be entered via either:-

This occurs when the exchange rate in the document header (either ENTERED by the USER or derived from the exchange rate table) differs by a larger amount than that specified as the MAXIMUM tolerance. (The message can CHANGED to be either an error or a warning).

This occurs when the exchange rate in the document header (either entered by the user or derived from the exchange rate table) differs by a larger amount than that specified as the maximum tolerance. (The message can changed to be either an error or a warning).

Defined in configuration they are SIMILAR to the FI validation rules above. SUBSTITUTION rules allow field VALUES to be replaced when certain pre-requisites CONDITIONS are met.

Defined in configuration they are similar to the FI validation rules above. Substitution rules allow field values to be replaced when certain pre-requisites conditions are met.

On the document header, the currency key is entered. If this is different from the ENTITY currency (or local currency), an equivalent amount in local currency is calculated automatically by the SYSTEM and stored in the field “local currency”. It is possible however to overwrite the system PROPOSED value in this field manually.

If the local amount is manually overwritten, and the difference between the implied exchange rate is SUFFICIENTLY different to the rate used by the system, a warning or error message is displayed (DEPENDING on system configuration).

On the document header, the currency key is entered. If this is different from the entity currency (or local currency), an equivalent amount in local currency is calculated automatically by the system and stored in the field “local currency”. It is possible however to overwrite the system proposed value in this field manually.

If the local amount is manually overwritten, and the difference between the implied exchange rate is sufficiently different to the rate used by the system, a warning or error message is displayed (depending on system configuration).

Parking is a SAP term which means a posting (AP/AR/GL) can be temporarily saved (possibly with incomplete information) without hitting the affected ledger(s). A separate person can then release the posting to the ledger when required.

This is useful for example if junior staff are to initially enter the invoices, before their SUPERVISOR checks it and books it to the ledger.

ANOTHER popular USE is when entering GL journals with many hundreds of LINE items. The document can be partsaved allowing for completion at a later date.

Parking is a SAP term which means a posting (AP/AR/GL) can be temporarily saved (possibly with incomplete information) without hitting the affected ledger(s). A separate person can then release the posting to the ledger when required.

This is useful for example if junior staff are to initially enter the invoices, before their supervisor checks it and books it to the ledger.

Another popular use is when entering GL journals with many hundreds of line items. The document can be partsaved allowing for completion at a later date.

Exchange Rate factors are the RELATIONSHIPS between ONE CURRENCY and ANOTHER to which an exchange rate is applied.

For example you may define the Indonesia Rupiah to US$ factor as 10000 : 1.

Combined with an exchange rate of 0.95 this would EQUATE to 9500 IDR to 1 USD.

Exchange Rate factors are the relationships between one currency and another to which an exchange rate is applied.

For example you may define the Indonesia Rupiah to US$ factor as 10000 : 1.

Combined with an exchange rate of 0.95 this would equate to 9500 IDR to 1 USD.

REASON codes are tags which can be ASSIGNED to EXPLAIN under/overpayments during the allocation of incoming customer payments. They should not be confused with ‘void reason codes’ used when outgoing checks are generated.

During configuration the following are determined

•  Whether the items booked with these reason codes are to be flagged as disputed items for the purposes of credit management (disputed items do not increase a customer credit exposure.
• The type of correspondence (if any) to be generated for this reason code as a result of the under/over PAYMENT.
• Whether a separate line item should be created to charge off the payment DIFFERENCES to a separate G/L account.

Reason codes are tags which can be assigned to explain under/overpayments during the allocation of incoming customer payments. They should not be confused with ‘void reason codes’ used when outgoing checks are generated.

During configuration the following are determined

Dunning is the process by which payment CHASING letters are issued to customers. SAP can determine which customers should receive the letters and for which overdue items.

DIFFERENT letters can be printed in SAP depending on how FAR overdue the payment is from a SIMPLE reminder to a legal LETTER.

The dunning level on the customer master indicates which letter has been issued to the customer.

Dunning is the process by which payment chasing letters are issued to customers. SAP can determine which customers should receive the letters and for which overdue items.

Different letters can be printed in SAP depending on how far overdue the payment is from a simple reminder to a legal letter.

The dunning level on the customer master indicates which letter has been issued to the customer.

A TEXT file is received from the BANK which is then uploaded into the SAP system. The file contains details of the company’s bank movements e.g. cheques, bank interest, bank charges, cash receipts etc. Depending on the system configuration SAP will attempt to BOOK these transactions AUTOMATICALLY to the correct accounts to avoid the NEED for manual entries by SAP users.

Any postings which the system cannot derive automatically can be booked through “post-processing”.

A text file is received from the bank which is then uploaded into the SAP system. The file contains details of the company’s bank movements e.g. cheques, bank interest, bank charges, cash receipts etc. Depending on the system configuration SAP will attempt to book these transactions automatically to the correct accounts to avoid the need for manual entries by SAP users.

Any postings which the system cannot derive automatically can be booked through “post-processing”.

The following STEPS are usually performed during the payment run

• Entering of parameters (company codes, payment methods, vendor ACCOUNTS etc).
• PROPOSAL Scheduling – the SYSTEM proposes list of invoices to be paid.
• Payment booking – the booking of the actual payments into the ledger.
• Printing of payment forms (cheques etc).

Variations on the above may be FOUND in different SAP customers, but the interviewer will be looking for the basis steps above.

The following steps are usually performed during the payment run

Variations on the above may be found in different SAP customers, but the interviewer will be looking for the basis steps above.

In certain industries (especially where there are a high VOLUME of cash TRANSACTIONS), it is not PRACTICAL to create new master records for every vendor trading partner.

One-time vendors ALLOW for a dummy vendor code to be used on invoice entry and the INFORMATION which is normally stored in the vendor master (payment terms, address etc) , is keyed on the invoice itself.

In certain industries (especially where there are a high volume of cash transactions), it is not practical to create new master records for every vendor trading partner.

One-time vendors allow for a dummy vendor code to be used on invoice entry and the information which is normally stored in the vendor master (payment terms, address etc) , is keyed on the invoice itself.

The baseline DATE is the date from which the payment terms (SPECIFIED in IMG transaction OBB) apply Usually this is the document date on the invoice but can also be the date of entry or posting date from the ledger.

The baseline date is the date from which the payment terms (specified in IMG transaction OBB) apply Usually this is the document date on the invoice but can also be the date of entry or posting date from the ledger.

Payment terms are created in CONFIGURATION and determine the payment due date for customer/vendor invoices.
They are stored on the customer/vendor master record and are PULLED through onto the customer/ vendor invoice postings. The due date derived via the payment can be CHANGED on each INDIVIDUAL invoice if REQUIRED.

Payment terms are created in configuration and determine the payment due date for customer/vendor invoices.
They are stored on the customer/vendor master record and are pulled through onto the customer/ vendor invoice postings. The due date derived via the payment can be changed on each individual invoice if required.

On the customer master there is a field “vendor” and likewise on the vendor master there is a field “customer”. By entering these master data numbers, a LINK can be created between the AP/AR subledgers for use in the PAYMENT program, dunning ROUTINE and the CLEARING of open items.

For example in the payment program, if a specific business partner is your vendor but also your customer, linking their master records together will allow the open AR invoices to be offset against the outstanding AP invoices.

On the customer master there is a field “vendor” and likewise on the vendor master there is a field “customer”. By entering these master data numbers, a link can be created between the AP/AR subledgers for use in the payment program, dunning routine and the clearing of open items.

For example in the payment program, if a specific business partner is your vendor but also your customer, linking their master records together will allow the open AR invoices to be offset against the outstanding AP invoices.

CHART of depreciation is the HIGHEST node in Asset ACCOUNTING and this is assigned to the company code. Under the Chart of depreciation all the depreciation calculations are STORED.

Chart of depreciation is the highest node in Asset Accounting and this is assigned to the company code. Under the Chart of depreciation all the depreciation calculations are stored.

The STEPS for Electronic Bank Statement are the same except for couple of more additional steps which you will see down below.

Step1: Create account symbols for the main bank and the SUB accounts.
Step2: ASSIGN accounts to account symbols.
Step3: Create keys for posting rules.
STEP4: Define posting rules.
Step5: Create TRANSACTION type.
Step6: Assign external transaction type to posting rules.
Step7: Assign Bank accounts to Transaction types.

The steps for Electronic Bank Statement are the same except for couple of more additional steps which you will see down below.

Step1: Create account symbols for the main bank and the sub accounts.
Step2: Assign accounts to account symbols.
Step3: Create keys for posting rules.
Step4: Define posting rules.
Step5: Create transaction type.
Step6: Assign external transaction type to posting rules.
Step7: Assign Bank accounts to Transaction types.