Common Business Requirement

Cash position report shows the balance in bank GL accounts and the bank clearing accounts. Before generating the cash position report, the bank GL accounts should be checked to see if there is any overdraft. If there is overdraft, interest should be calculated and journal entries posted for the overdraft interest such that the cash position report will be reflective of actual cash position.

Detail and Design

SAP provide the standard SAP Cash Management and Forecast Report for cash position report. This SAP report can be used for both cash position and liquidity forecast.

On the selection screen, if only the Cash Position checkbox is checked, then only cash position is displayed. If the Liquidity Forecast checkbox is checked instead, then liquidity forecast is displayed.

Planning Levels

The balances in bank GL accounts and bank clearing accounts will form part of cash position if the planning levels set in the company code level of the GL account master are indicated as relevant for cash position. Planning level is either relevant to cash position or liquidity forecast. Planning level is classification of causes of bank transactions.

Since planning level is entered at the company code level in the GL account master, new countries will decide on mapping of planning level to bank and bank clearing GL accounts.

Grouping

Grouping is a 10 characters code which must be entered when generating the cash position report. Grouping determines what information is shown in the report. For example, if country often has to view only outgoing payment related cash information, then a grouping “OUT_PAYMNT” should be created such that balances of accounts belonging only to outgoing payment planning levels are displayed when this grouping is selected. Grouping is also applicable to liquidity forecast.

Summarization Term

Summarization term is assigned to grouping and group together individual accounts in the cash position report display.

For example, if the country only needs to see the balances (and not the details) in all outgoing clearing accounts and outgoing bank GL accounts, then summarization term “OUT_PAYMNT” should be created such that the first screen of the report will only display the sum of these accounts under summarization term “OUT_PAYMNT” instead of showing the balances of individual outgoing clearing accounts and outgoing bank GL accounts.

The length of summarization term is also 10 characters. Summarization term is also applicable to liquidity forecast.

Viewed 9196 times by 3434 viewers

Bookmark SAP Tutorial:

Common Business Requirement

Bank statements reflect movements in bank balances resulting from various activities such as loan/deposit interest, overdraft, incoming payment from customers and outgoing payment to vendors.

Periodically, bank statements are either downloaded from bank websites or are sent to your company by the banks. Where bank statements are in MT940 format (format compatible for uploading in SAP), the bank statements will be uploaded.

If banks are able to provide information on the line items in the bank statements, upon posting of the bank statements, bank clearing accounts (e.g. incoming and outgoing clearing accounts) will be cleared.

Where banks are not able to provide information on the line items, the bank statement will be posted and clearing will be done subsequently (either manually or automatically). Sometimes, due to technical reasons, some line items in the bank statement may not get posted.

In this case, post processing is required where user will determine how these line items will be posted. Where bank statements are not uploaded, they will be manually entered into the system. After electronic/ manual bank statements have been posted, bank reconciliation should be carried out. In bank reconciliation, investigation is carried to check why there are unmatched items in the clearing accounts.

Detail and Design

Bank Accounts and GL Accounts

In general, the company has separate bank accounts for incoming and outgoing payment. For each bank account, there will be a main bank GL account and one or more clearing accounts. The main bank GL account will be created as allowing automatic posting only.

During incoming or outgoing payment transactions, the bank clearing accounts will be debited/ credited. When bank statements are posted, the bank clearing accounts will be debited/ credited and the main bank GL account will be debited/credited. In this way, the main bank GL account balance will always be equal to the actual bank account balance.

Electronic Bank Statement

The following settings need to be made for electronic bank statement:

• Bank accounts are assigned to transaction types. Transaction types represent the type of bank statements which company receives. For example, a country has one bank account for payment with Citibank and one bank account for payment with Deutsche Bank. These two bank accounts will be assigned to two different transaction types, as the information provided on the bank statements of both banks will be different.
• External transactions are assigned to transaction types. External transactions are abbreviations on bank statements which indicate the type of transaction (e.g. bank transfer, cheque deposit) from the bank’s perspective.
• Posting rules are assigned to external transactions. Posting rules determine the posting keys and document types used in posting the bank statement. For example, if the external transaction is incoming payment, the posting rule will specify that the incoming payment bank GL account should be posted with posting key 40 and the incoming bank clearing account should be posted with posting key 50. Posting rules also determine if the bank clearing accounts are cleared at the time of bank statement posting. In addition, posting rules determine which GL accounts get posted via account symbols.
• Account symbols are assigned to GL accounts. For the same account symbol, different GL accounts can be assigned for posting using different currencies.

Addition configuration will be required for each new country due to different bank accounts and bank statement contents.

Manual Bank Statement

When posting manual bank statements, user needs to enter manual bank statement transaction. Manual bank statement transactions are assigned to transaction types and the remaining settings is similar to electronic bank statement. Addition configuration will be required for each new country due to different bank accounts and bank statement contents.

Viewed 8236 times by 3173 viewers

Bookmark SAP Tutorial:

Common Business Requirement

Each bank which your company deals with should be created as a bank master inside the SAP system. After request to create/change bank master has been approved, bank master is created/changed in the SAP system.

Where the company no longer deals with a particular bank, the bank master should be flagged for deletion. Periodically, changes made to bank master data should be reviewed to ensure that changes made were authorized and accurate.

Detail and Design

In SAP system, each bank master is uniquely identified by bank country and bank key. Where payment is received from customer or made to vendor via bank transfer, bank data of the customer/vendor (bank country, bank key and account number) should be maintained in the customer/vendor master.

Before bank data can be maintained in the customer/vendor master, bank master should be created.

In addition, where the company uses new banks to make payment, the bank master can first be created or created at the same time when house bank is being defined in the configuration in SAP system. One bank master can be linked to numerous actual bank accounts.

Viewed 7075 times by 2782 viewers

Bookmark SAP Tutorial:

Mostly the transaction code always shows as SPRO. There are many ways to get the SAP transaction code.

1. In SPRO screen -> Select Additional Information -> Display key -> IMG activity.
   
   Now SPRO screen will split into 3 parts. It will display some the corresponding details. The SAP transaction code name will be the last four digit of the detail displayed against the selection.

   For example, SIMG_CFMENUSAPCOX10. So the SAP transaction code is COX10.

2. Place the cursor on the IMG activity that interested you, activate the context menu by right mouse button click and select the Display Technical Info function then.
   
   In the Maint.Obkect tab strip of the selected IMG activity, you can find information relate to the update, the customizing view and the SAP transaction code
3. SPRO screen, check the SAP program name by going system > status from menu and trace from TSTC table via SE16 transaction

Viewed 6452 times by 2810 viewers

Bookmark SAP Tutorial:

Common Business Requirement

At period-end, vendor line items and balances should be analysed to ensure accurate postings and that the same vendor invoice was not posted twice in the SAP system. Following types of SAP reports are available

• Vendor balance reports
• Vendor line item reports
• Vendor payment analysis reports
• Duplicate invoice reports
• Vendor master reports

The custom SAP report, Vendor Payment Analysis report and BW report Vendor Balance Details should also be generated.

Detail Analysis

Standard AP reports are in ALV format which enables users to add/remove standard fields from reports to customize the reports according to their business needs.

The custom report Vendor Payment Analysis report should be generated if user needs to check which invoices are due or overdue for payment and download the information into excel.

This report is required as standard SAP report providing this information is not in ALV format and thus cannot be downloaded efficiently into excel.

The BW report, Vendor Balance Details should be generated to analyse payables by reconciliation accounts, document currency and special GL indicators.

Viewed 8825 times by 3650 viewers

Bookmark SAP Tutorial:

Common Business Requirement

The most common form of correspondence that the company sends to vendor is balance confirmation letter. In general, balance confirmation letter will be sent via email to vendors.

Detail Analysis

Depending on audit and legal requirements in individual country, balance confirmation letter will be customized with local language and specific format. The custom program Print Program: Account Statement is used to email the balance confirmation letters to vendors.

Viewed 9727 times by 3747 viewers

Bookmark SAP Tutorial:

Common Business Requirement

To calculate vendor interest using the SAP system, interest indicator needs to be maintained. Thereafter, there are several ways to calculate vendor interest:

• Calculate interest without open items.
  The SAP system calculates interest on cleared vendor items (late payments) and post the interest.
• Calculate interest with open items.
  The SAP system calculates interest on open (overdue) vendor items and cleared vendor items and posts the interest.
• Calculate interest without posting.
  The SAP system calculates interest on open and/or cleared vendor items and does not post the interest.

Viewed 10023 times by 3694 viewers

Bookmark SAP Tutorial:

Common Business Requirement

Manual clearing of vendor account is required where staff advance is posted in SAP system via special GL indicator. When the payroll text file from SAP HR system is uploaded, there will be a credit posting to the staff advance special GL account.

Hence, clearing of the staff advance special GL account must be performed by vendor account number via the account payable (AP) manual clearing function.

Detail Analysis

Clearing of vendor account is only necessary if staff advance is posted via special GL indicator. Where staff advance is not posted via special GL indicator or where staff advance is not handled in SAP system, clearing of vendor account will not be required.

Viewed 10056 times by 3649 viewers

Bookmark SAP Tutorial:

Common Business Requirement

Staff advance will be handled within the account payable (SAP AP) module if the country is not using any other application (e.g. SAP Travel Management) to handle staff advance.

Advances will be given to employees by company for approved purposes such as travelling or housing expenses. Advance payment can be made via payment run (automatic payment program) or manually.

After the staff advance has been posted in SAP system, the information will be passed to the Human Resource Department. Standard Vendor Balances in Local Currency report or customised Main Account Detail report will be generated to extract the staff advance information.

The Human Resource Department enters this information into the SAP HR system and after calculating the payroll, a text file will be generated from the SAP HR system which is then uploaded into SAP for journal posting.

Detail Analysis

In order to post staff advance via special GL indicators, employees must be created as vendors in the system. For all other types of staff advance, posting will be made to relevant staff advance GL accounts directly.

Viewed 10697 times by 3652 viewers

Bookmark SAP Tutorial:

Common Business Requirement

Where agreement with the vendor is such that a payment must be made before receipt of goods or services, down payment will be made. Basically, there are three ways to make down payment:

• Post down payment directly.
• Post down payment request and then post down payment with reference to down payment request. Down payment request creates a noted item against the vendor.
• Post down payment request and pay via the automatic payment program via F110 transaction.

Normally, letter of guarantee will be posted via statistical posting function.

When invoice pertaining to existing down payment or letter of guarantee is posted, the SAP system issues a message informing about the existing down payment or letter of guarantee. Thereafter, down payment should be cleared or letter of guarantee reversed.

Detail Analysis

Special GL Indicator for Vendors

Down payment to vendors will be made via special GL indicators. Special GL indicators allow posting to be linked to the vendor account even though the actual GL account which is being updated is the down payment GL account. When down payment to vendor is posted, the down payment GL account is debited and the bank outgoing clearing account is credited.

Even though the down payment GL account is updated, when viewing vendor line items, the down payment will be reflected as a special GL transaction item.

When down payment is cleared against the invoice, the vendor account is debited and the down payment account credited. Hence, after clearing, the balance in the down payment GL account is zero and the amount of down payment made is transferred to the vendor account to offset the amount payable to the vendor.

Statistical Postings

Letter of guarantee is handled via statistical posting. When posting the letter of guarantee, a special GL indicator must also be entered. The statistical posting will debit a balance sheet guarantee GL account and credit a balance sheet guarantee offsetting GL account. In this way, the net impact on the balance sheet is zero. When viewing vendor line items, the letter of guarantee is shown as a noted item.

Viewed 10652 times by 3488 viewers

Bookmark SAP Tutorial:

The alternative way to make paymemt are:

• Manual Payment
• Cheque Lot Maintenance

Manual Payment

Unlike in automatic payment via F110 Transaction, when making manual payment in SAP, only one vendor can be paid at a time. Also, the bank clearing account from which the payment is to be done must also be manually entered. Moreover, the specific invoice in SAP syetem to be paid must be manually selected.

Cheque Lot Maintenance

For facilities using cheques with pre-printed numbers to settle their payables, SAP system can be configured to keep track of their cheque numbers usage in the system to ensure fraud is prevented. This can be done by utilizing the cheque lot management functionality.

The following can be done through cheque lot management:

• Create a cheque lot with the corresponding cheque number range as given by the bank. Multiple cheque lots can be maintained as needed.
• Whenever the payment method for cheque printing is specified, the payment program will select the first available cheque number from the correct check lot (as specified by the user) and attach it to the payment document. Therefore, every cheque number is accounted for. Cheque numbers will not be utilized more than once.
• Cheques can be voided and audit trail is available as user ID is attached to a voided cheque. Every voided cheque needs to be tied with a void reason code.

Make payment via Automatic Payment Program

Viewed 10218 times by 2781 viewers

Bookmark SAP Tutorial:

The automatic payment program in SAP selects appropriate invoices to be paid based on the following parameters

• Documents entered up to. The program selects invoices entered in SAP system with entry date up to the date specified in this field.
• Next payment run date. The program selects invoices in SAP system which will be overdue or incur lost cash discounts if paid on the date specified in this field.

When executing the automatic payment program (F110 transaction), a proposal run must always be carried out in SAP system first. The proposal list will sometimes include exceptions.

Common exceptions are:

• SAP Invoice contains payment block. To pay this invoice, remove the payment block when editing the proposal list (unless the payment block is one which cannot be edited during payment proposal) or remove payment block via FB02 for each SAP invoice.
• Payment method in vendor master/invoice is different from the one specified in the payment program parameter. To pay this invoice, allocate the payment method in the parameter of the payment run to this invoice while editing the proposal list.
• Vendor master does not contain information specified as mandatory in the payment method in the parameter of the SAP payment program.For example, depending on the payment method configuration for the country, certain fields such as city or PO Box must be populated in the vendor master. In this case, delete the proposal run, make the necessary changes in the vendor master and execute the proposal run again.

Typically, payment program pays due invoices in full. To cater for partial payment via automatic payment program, payment request will be used (optional). Down payments to staff and vendor can also be made via the automatic payment program if down payment request was posted.

If foreign currency invoice is paid via automatic payment run, the relevant exchange rate type should be selected in the payment run parameter. Exchange rate gain/loss on making the payment will be automatically posted to the relevant profit and loss account based on the reconciliation account of the vendor.

The payment method specified in the parameter of the payment program determines the bank account and the GL account used to make the payment. Also, depending on the payment method, cheques, other forms and payment files will be generated.

The due invoices in SAP for the same vendor in the same payment run will be cleared by a single payment document.

After automatic payment run, the remittance advices can be generated automatically for each vendor and printed or sent via email. For email option, Acrobat Reader (PDF) file containing remittance information is created and attached to email.

Alternative ways to make payment:

• Manual Payment
• Cheque Lot

Viewed 12788 times by 3630 viewers

Bookmark SAP Tutorial:

Common Business Requirement

After invoices have been posted in SAP system, payment should be made timely so as to realize cash discounts and avoid late payment interest. In general, the company makes payments to vendors (including staff advances where staff advances are posted in SAP) via one of the following payment methods:

• Cheque
• Bank Transfer
• Electronic Bank Transfer
• Demand Draft
• Cash

Generally, countries will base the decision on which payment method to use depending on whether the vendor is a local or foreign vendor.

Payment method will be maintained in the vendor master in SAP system. During invoice entry in the SAP system, the payment method is defaulted to the payment method maintained in the vendor master. If required, the default payment method can be manually overwritten during invoice entry in SAP.

Apart from paying vendor invoices, outgoing payment functions in SAP will also be used to make payment to tax authority if the tax authority is defined as a vendor in the SAP system. Otherwise, tax will be paid via outgoing payment function in the General Ledger (SAP GL) module.

For ad-hoc payment, the individual invoice to be paid will be manually selected for payment. For periodic payment, automatic payment run will be used where invoices due for payment will be selected by the SAP system based on parameters entered in the automatic payment program (F110 transaction). Before executing the automatic payment run, invoices should be reviewed to see if blocking/unblocking of the invoices is necessary. If payment is to be made using cash, the payment will be recorded using SAP Cash Journal.

Optionally, after executing automatic payment run in SAP, approval will be done in SAP before the payment file is sent to the bank. Also, after executing automatic payment run, the SAP system will email payment advices to vendors. If payment is not made via automatic payment run, payment advices are not sent to vendors thru SAP system. Email address is taken from vendor master data on general screen in SAP.

Cheque printing can be done during manual payment or automatic payment. Cheque lots need to be maintained in the SAP system in order to link cheque number to the payment document. Where electronic payment is involved, after the payment has been executed in the SAP system, a payment file will be generated and transmitted to the bank.

Depending on agreement with the customer, payment will either be made to customer for customer credit memo or credit memo will be used to offset against subsequent customer invoice.

Analysis and Design

• Automatic Payment Program
• Manual Payment
• Cheque Lot Maintenance
• Reporting

Viewed 11028 times by 3105 viewers

Bookmark SAP Tutorial:

Common Business Requirement

Prior to making payment in SAP, invoices should be reviewed to check if they should indeed be paid. For example, if there is an unresolved dispute with the vendor on the amount payable of an invoice which has been posted some time ago, recent invoices should be immediately blocked for payment after posting in SAP system. After the dispute has been resolved, the invoices should be unblocked for payment.

For PO invoices, invoices are automatically blocked in SAP for payment if tolerance limit is exceeded. Unblocking of PO invoices blocked due to variance should be done using via the Release Blocked Invoices function in SAP Materials Management (SAP MM) module.

When editing the proposal list via F110 transaction, invoices should also be checked if they should be blocked/ unblocked for payment.

Design

An invoice is blocked for payment if the payment block field in the invoice contains a payment block reason code. Such an invoice will fall into the exception list during payment proposal run.

• If a payment block reason code is editable in payment proposal (F110 transaction), this means that the payment block reason code can be set or removed when the proposal list is being edited.
• If an invoice is blocked for payment by a reason code which is blocked for manual payment, the invoice cannot be selected for payment during manual payment.
• If the reason code is non-modifiable, it cannot be set or removed using the change document function in the General Ledger (SAP GL) module thru FB02 transaction.

Viewed 12815 times by 3637 viewers

Bookmark SAP Tutorial:

Non-PO credit memo will be posted in the SAP Account Payable (AP) module. Depending on the standard operating procedure within the country, the credit memo will first be parked and only posted upon approval/ review, or directly posted.

If there are many items on the credit memo, the fast entry function provided in SAP should be used.

Design

Posting of credit memo creates an open debit item on the vendor account. Credit memo offsets the amount payable to the vendor and both the invoice and credit memo will be cleared during payment process.

Viewed 13782 times by 3648 viewers

Bookmark SAP Tutorial:

Non-PO invoices will be posted via the SAP AP module in SAP Financial Accounting. Typically, non-PO invoices arise due to non-stock and non-production item purchases e.g. utilities and telephone bills. It is possible that a goods receipt is performed without reference to PO (e.g. returnable packaging material). In this case, if the vendor invoices company, the invoice will be posted as a non-PO invoice in the SAP AP module.

For non-PO invoice, the invoice processor needs to manually verify that the invoice has been approved by authorised personnel in the requesting department and that relevant supporting documents have been provided.

Depending on the standard operating procedure within the country, invoices will first be parked, and only posted upon approval/review, or directly posted. If there are many items on the invoice, the fast entry function should be used.

Certain invoices, such as rental will be received monthly. For such fixed monthly expenses, recurring entry function can be used to post the invoice. After posting the invoice, there may be a need to block the invoice for payment. If the invoice is not blocked for payment, it will be paid on or before the due date based on the vendor payment terms.

If down payment had previously been paid to the vendor, at the time of posting the invoice, the system will display a message with this information. After posting the invoice, down payment should be cleared against the vendor.

On vendor master data in SAP system, trading partner field can be used for reconciliation between Inter companies. For each country there was only on company, each company code will be defined as company and there will be one to one relationship between company and company code. These companies are assigned to vendor master data as trading partner.

At time of document posting in SAP system, trading partner will be transferred to line item so that the elimination functions can be carried out within consolidation.

Alternative reconciliation usage:

Only one customer/vendor is created and one reconciliation account is assigned to master data. But you define the alternative reconciliation accounts allowed for each reconciliation account. At time of master data definition, reconciliation account which is used very often should be assigned to vendor/customer master data. You can also specify a short key for each alternative reconciliation account which enables you to work more quickly during document entry. So at time of document entry, user has to choose reconciliation account.

Design

Payment Terms

Payment term is a 4 character alpha numeric code maintained in the company code view and/or the purchasing organization view of the vendor master. During invoice entry in SAP system, the payment term is defaulted to that maintained in the vendor master and can be overwritten.

Payment term controls the following:

• Baseline date default. Baseline date is the date starting from which the invoice due date is calculated. The payment term can be configured to default the baseline date to posting date, document date or entry date.
• Discount. The percentage of discount as well as the number of days within which payment needs to be made in order to realise the discount
• Payment due date. The number of days after the baseline date when the payment has to be made.

Payment terms are set up based on the existing arrangements with the vendors in the various countries.

Where discount is realised upon payment of invoice, the discount taken is posted to GL account as CASH DISCOUNTS RECEIVED.

Posting Invoice in Foreign Currency

When an invoice is posted in foreign currency, the SAP system stores the amount in both local and foreign currency in each line item.

There are several ways in which foreign currency invoices can be posted:

• Enter the foreign currency in the document header. The system automatically translates the foreign currency to local currency based on the exchange rate maintained in the system that is applicable on the posting date.
• Enter the foreign currency and the exchange rate in the document header. The system translates the foreign currency to local currency based on exchange rate entered inn the document header.

Viewed 14943 times by 4520 viewers

Bookmark SAP Tutorial:

Basically, the processes covered within SAP Accounts Payable (AP) blueprint are:-

• Vendor Invoice Entry
• Vendor Credit Memo Entry
• Block/Unblock Vendor Invoice
• Outgoing Payment
• Down Payment to Vendor
• Down Payment to Staff
• Clear Accounts Payable
• Accounts Payable Interest Calculation
• Correspondence with Vendors
• Tax
• Accounts Payable Reporting

Viewed 13179 times by 3969 viewers

Bookmark SAP Tutorial:

Anyway, you can only migrate from the classic GL to the new GL after you upgrade your SAP R/3 system to SAP ERP.

You must prepare and execute this migration project with the utmost care to ensure accounting is still in order after the migration.

What should we consider when upgrading the new general ledger in SAP ERP?

Solution – read SAP Note 812919 on SAP Service Marketplace.

To ensure maximum security, SAP supports each migration project with the SAP General Ledger Migration migration service. This mandatory technical service is based on standard migration scenarios and includes a scenario-specific General Ledger Migration Cockpit and service sessions to ensure the quality of the data and of the migration project. The service sessions are provided by a NewGL migration back office, which was specifically set up for this purpose.

After you commission the service, you are provided with the General Ledger Migration Cockpit and the service sessions are delivered after consultation.

The migration service contains the following functions:

• General Ledger Migration Cockpit for executing the migration
  • Process tree with scenario-based management by the individual activities of the migration
  • Monitor of the migration steps with status management

• Remote service session to validate the scenario and analyze the system
  • Possible consistency checks against target Customizing of the new general ledger accounting

• Remote service session to validate tests
  • Technical validation checks in a test system after a data migration

• Development support by the NewGL migration back office

For more information about this migration service with a description of the migration scenario, a migration guide and other useful information, see SAP Service Marketplace at: http://service.sap.com/GLMIG

Viewed 19923 times by 5639 viewers

Bookmark SAP Tutorial:

The new General Ledger in mySAP ERP 2004 has the following advantages over the classic General Ledger in SAP R/3 Enterprise:

• In the new General Ledger, you can display the parallel accounting using parallel accounts (as in SAP R/3) or using parallel ledgers. The FI standard functions and reports are available for all parallel ledgers.
• The ‘Segment’ entity and the relevant reporting that are required for segment reporting according to IAS and U.S. GAAP are available in the new General Ledger.
• In addition, you can enhance the new General Ledger flexibly, that is, you can enter user-defined fields and update the relevant totals. Many standard reports can evaluate the information from the user-defined fields.
• When you use the new ‘Document Splitting’ function (online split), you can create financial statements at company code level and, if required, for entities, such as the segment. For each document, the system then creates a zero balance for the relevant entity, for example, for the segment.
• As a result, you no longer have to carry out time-consuming reconciliation tasks between FI and CO for the end of period since cross-entity processes are transferred in real-time to the new General Ledger in Controlling. Furthermore, you can, for example, navigate from the financial statements report results or the profit and loss statement report results to the relevant CO report.
• The new General Ledger uses the same interfaces as the General Ledger in SAP R/3. As a result, users do not require any additional training.
• Due to the new ‘multi-dimensional’ aspect in the General Ledger, all data that is relevant for the General Ledger is stored in one environment. As a result, reconciliation tasks, for example, between the general ledger and Profit Center Accounting or the consolidation staging ledger, and processing steps that have to be carried out repeatedly in the individual applications (for example, balance carryforward) are no longer required. When you use the new General Ledger, you may not have to use the special ledger anymore.

Default delivery

In new installations, the new General Ledger Accounting is activated by default in mySAP ERP. We do not recommend that new customers use the classic general ledger accounting since using the classic general ledger accounting requires additional migrations at a later stage. As a result, new customers require explicit authorization from SAP to use the classic general ledger accounting. If you want to use the classic general ledger accounting. create and send a CSS message to SAP before you start using the system.
When you upgrade an SAP R/3 system to mySAP ERP, the classic General Ledger remains active at first. If you want to convert your system to the new General Ledger, you can do so within a project after you have completed the upgrade. For more information about this topic, see point 3.

Migration support

To ensure maximum security, SAP supports each migration project with a migration service. This basic technical service is based on standard migration scenarios and is provided in the form of migration packages for a fixed price.

This service is provided by a NewGL migration back office, which was set up for this purpose. After you commission the service, the Migration Cockpit is available to download to the Service Marketplace.

For information about the SAP General Ledger Migration Service, see www.service.sap.com/glmig.

Release restrictions

Check SAP Note 741821.

Viewed 20668 times by 5599 viewers

Bookmark SAP Tutorial:

• If a three way match exists, the invoice will be ready for payment automatically thru SAP system.
• If a three way match does not exist, the vendor invoice will be blocked for payment until the discrepancy
  can be resolved.

There are two types of invoices will be received in SAP system:

1. Direct invoices – Invoice that exist without a purchase order (PO) or goods receipts (GR) via FB60 transaction
2. Purchase order invoices – Invoice that is received from a PO via MIRO transaction

During Invoice Verification for Purchase order invoices (MIRO)

• Incoming invoices and credit memos are entered, Invoices are checked for accuracy and correct prices
• Resulting account entries are posted
  

  Credit Vendor account
  Debit GR/IR account

• Miscellaneous data are updated in the SAP system

Viewed 24165 times by 6609 viewers

Bookmark SAP Tutorial: