2. Customizing tables used by Golden Audit Report:In addition to maintaining the Financial statement version as described above we need to perform certain configuration steps as explained below.

IMG > Financial Accounting > General Ledger Accounting > Business Transactions > Closing > Report > Legal Reporting China

• Maintain Currency Codes

The first column represents the report number i.e. 6 in case of Income statement. Internal item id flows from FSV where it is maintained as 3 digit number followed by text ‘P_06_’.

The Report Item ID and Report item content are provided by Chinese authorities and this is to be maintained as per the latest PRC GAAP.

• Maintain Detail Expense Account

In this step we maintain the relationship between the Chinese detail expense account and Chinese first level expense account as required by Chinese authorities

The account number of the Chinese detail expense account to be used, with the corresponding Chinese first level expense account and text, as defined by the Chinese Government.

• Maintain Map Expense Accounts

In this step we maintain the relationship between the G/L account, Functional Area and Chinese Detail expense account. If we maintain Functional area in financial statement versions then report output would show balance per Chinese detail expense account instead of list of G/L accounts.

Client usually make customized report and in that case testing of data takes place and many times testing gets correct but they miss out essential part required at time of using special purpose ledger is using Tcode GWUL .

GWUL is used for refreshing customized report made in report painter like trial balance , balance sheet , cashflow statement , segment reporting etc

This GWUL is used when transaction are taking place in foreign currency and reporting is required in some other currency . So essentiality is both currency should be different .

Tcode GWUL

I will explain from point of balancesheet where reports are extracted at any period of time .But exchange rates keeps on changing on daily basis in that case such balancesheet report need to be refreshed to latest exchange rates . This is where GWUl is used . GWUL refreshes Balancesheet at latest exchange rates and post difference to defined GL accounts called as translation difference account .

How to find Translation difference account?.Tcode GCW4Below screenshot shows that GL 32001 is where Translation dfference will be posted

.

Now Will check how this this exactly works

Will take balance sheet for period 6 FY2014

Make note of GL10001 in Company code 0070

After some months there is again requirement for balancesheeet .We assume that no transation has been posted in between periods .

Will run GWUL for Period 9 Fy 2014 so as to refresh balancesheet to exchange rate available for Period 9 Fy 2014 .

This is how GWUL will show details .

Now will reopen Balncesheet for period 9 FY14

So now We can see balances are changed in GL 10001 and Balance sheet is tallied and balance is shifted to "TRANSLATION DIFFERENCE ACCOUNT"

Also we can check that translatn diff amount in after running GWUL above tallies with amount available in balancesheet .

Regards

kaushal Ghedia

BACS payments are domestic, non-urgent payments (ACH payments) in the United Kingdom of Great Britain and Northern Ireland. Processable amounts are limited by the credit limit set by the BACS clearing system only. Traditionally, the BACS format is using the text flat file uploaded to the bank.

In 2014, SEPA, which stands for Single Euro Payments Area, is an initiative in the European Union to simplify the bank transfers. While the rollout for non-Euro member states like the United Kingdom is expected to transition by early Q4 of 2016. Banks located in the United Kingdom is already moving towards this direction. The document describes some tips in using the SEPA Credit Transfer format for UK-BACS in SAP.

Tip #1: It is best to reference SAP supplied format into a Z-format for modification.

To create a DMEE format using a reference format, enter the following information

• Transaction Code: DMEE
• Tree Type: PAYM
• Reference format tree: SEPA_CT

1- Create a new format tree: ZSEPA_CT

2- Click on the icon copy . In the source tree, it is possible to define the source structure and the target structure

3- Click on Copy  to proceed with the copy of reference DMEE tree. A transport pop-up screen will show to save the Workbench Transport if you are in a development client.

Copying from SAP template as reference has some advantages namely:

• Inexpensive. It allows you to leverage on the pre-set structure/format in order to save time vis-a-vis developing the DMEE tree from scratch
• Ready to go. You can start modifying your DMEE tree more or less instantly. It reduces the complexity in development.

Tip #2: Amend the overall structure to correspond to the output requirement of the bank

In order to visualize DMEE format tree, it is best to look at the screen with two sides. On the left hand side is the XML structure which can be changed according to the bank’s file requirement format.

On the right hand side represent the field mapping for each node. It can be changed according to the bank’s requirements. It represents the different mapping procedure which is flexible to cater for the bank’s requirement. If the standard mapping procedure, there is always an option of writing a user exit.

It is easy to check if the overall structure correspond to the output requirement of the bank. Just compare the

Tip #3: Managing Sort Codes of Beneficiary account using Vendor Bank Master Data

The beneficiary account is addressed via the sort code of the beneficiary's bank and the (domestic) account number. This includes the bank's sort code and the bank account number of the beneficiary.

To manage this data, it is recommended to organize the coding structure of vendor bank master for UK vendors as follows:

IBAN and SWIFT code is generally not required for BACS payment. However, it will be useful for future Euro payments and both can be stored in the vendor bank master.

Below is an example. (Data is for sample only to illustrate the mapping structure)

Maintaining the integrity in the vendor bank master data reduces any possible issues in processing with bank. There are a few sites recommended for the checking the validity of sort code:

UK Payment Council's sort code checker:

Payments Council - Sort Code Checker

UK Payment Council's IBAN checker:

Payments Council - IBAN Checker

Tip #4: Including a control sum checks on the number of transactions

By default, the SAP's template SEPA_CT format includes a control sum checks. Depending on the bank's requirement, changes can be made to include a control sum checks into the DMEE file.

The following is a simple explanation to understand the use of reference IDs and the aggregation as a counter in the DMEE format tree.

In the sample file, <NbOfTxs> 2 </NbOfTxs>is a control sum of the number of transactions expected to be process in the <PmtInf> file. It counts the number of <CdtTrfTxInf>.

In the NbOfTxs node, aggregation is used as the mapping procedure

In the aggregation tab, it uses the reference ID “TX” as a point of aggregation and aggregation rule to use is 2. Below are the standard aggregation types and its descriptions.

This reference ID is linked to the node <CdtTrfTxInf>

Tip #5: Ensure that the XML encoding with the correct format

The encoding specification in the file does not match the code page entered.

The issue as described in the SAP note states, “The XML file contains the specification encoding="UTF-16", although the code page 4410 has a UTF-8 in transaction”

Pls. refer to the SAP notes below for more information:

SAP Note 1954679

SAP Note 1841190

Introduction

Check printing is the most common form of the payments however nowadays with more and more companies are automating their payments and submitting their payments to banks in electronic format due to cost effectiveness,security and ease.

There are multiple Bank transfer formats available and usually differ by country.

However we will be focusing on the creation of the Bank transfer file submitted to Banks from the USA perspective though please note that the configuration steps are very similar in other types of formats.

As of release 4.6C , the Payment Medium Work Bench was introduced which is a generic payment medium program  and can be used  in place old payment medium program RFFOUS_T US Domestic Bank Transfer.

In this document we will explain the creation of NACHA format file ( National Automated Clearing House Association) which need to be submitted to Banks for processing the ACH ( Automated Clearing House) transaction.

Configuration Steps

Step 1 Ensure that country specific checks are set to these values Transaction code OY17

Step 2 Please ensure that all the setting have been maintained for the Automatic Payments using the transaction code FBZP

As shown in the below screen shot by going on each tab. For processing the ACH payments we need to use the Payment Method T

2A Click on  All company codes tab and make the settings by clicking the new entries  in our case we have the Paying and sending company codes as same though it can be different

2B Click on the paying company code and make the settings

2C Click Payments method country and update the selection to use Payment Medium Work Bench

We are using the format ACH which is for US domestic Transfers. ( there are also other formats available for USA which you can use based on your requirements)

We are using the CTX as format supplement however there are other format supplement also available.

Please see the below screen shot.

2D Make the settings for Payments method in company code

2E Make the settings for the Bank Determination and make the settings for each section as shown on the left corner on screen shown below

2F Make the settings for the House banks and bank accounts (You can go directly from the house bank Tab in FBZP or  use House Bank  Transaction code FI12)

Create the house bank with below settings as shown in the screen shot and its important to maintain these settings to correctly create a NACHA file format

After maintaining the fields as shown in the below screen shot click on change tab as shown in the screen shot

In the below Pop up screen maintain the Bank Address data. The grayed out fields have been auto populated based on the earlier settings as shown in the previous screens

Expand the EDI Tab and update the company number which the company Tax identification number. Please add 1 before the number of your company

Click on the Bank Accounts on left side of the House Bank Screen  and update the details of the GL and Bank Account number, Control key etc use 01 for checking account in control key

Step 3 Execute the transaction code OBPM1 which shown the payment medium formats. We will using the ACH format and use the SAP standard settings and will not be modifying anything in the standard settings. You can double the selected ACH format to review the settings.

Step 4 Create the Payment medium selection variant. Transaction code OBPM4 and in the screen mention the Payment variant and click on the arrow next to it and it will ask whether you want to create payment variant as shown in the below screen and you need to click on Yes

Make the selection as shown in the below screen shot and press continue

Update the settings as shown the below screen shot and and also click on the tab Format Parameters and Maintain small screen pop too with identification what are you paying and also company identification ( Your company EIN/TIN with suffix of 1) and Save it

Step 5 Please make sure the Vendors Bank master data is maintained  and Payments method is maintained in the Vendor master records.

Step 6 Execute the Payment run using the Transaction code F110  and in the parameter screen select the payment method as T and once the payment run have been completed ACH NACHA file will be generated.Please note we are not covering the steps how run a payment run.

Once the payment run have been completed go the Environment -Payment Medium and then select DME Administration  ( Transaction code FDTA)

Though the NACHA file would have already downloaded in the directory defined in the earlier settings which may be secured FTP/Local Machine/SAP directory .

However below screen shows you how to access the file and download it again

Double click on the selection and click on down load on the pop up screen you can see the NACHA file which have been downloaded and you can again down load the same . (You can see the spool using the transaction code SP02)

Please see the below screen shot showing the NACHA file created which can be transmitted to Bank for processing the ACH payments.

Hello, SAPers!

Here is a small tip on defining tax codes per transaction. For some of you, especially those with wide and long experience in FI module, this post might be trivial, but it might be interesting for consultants that just started on their career path.

Customizing of country’s tax scheme very often involves a lot of tax codes, which can be linked together into so called chains of tax codes (deferred versus target tax codes). Many of these target tax codes are used solely for reporting purposes via different tax grouping versions (OBCH / OBCG) and are not used by users in their daily operations. Nonetheless, these technical tax codes appear in drop-down lists in transactions FB60 / FB70 / MIRO etc. and cause inconveniences for end-users to select the right tax code.

Fortunately, SAP provides standard solution that enables you to manage the visibility of tax codes in financial and logistics transactions. In order to configure the settings go to transaction OBZT. Alternatively, you can use the following menu path:

IMG → Financial Accounting (new) → Accounts Receivable and Accounts Payable → Business Transactions → Outgoing (or Incoming) Invoices/Credit Memos → Outgoing (or Incoming) Invoices/Credit Memos - Enjoy → Define Tax Code per Transaction

Specify the country key in the pop-up windows and press Enter. Once in the transaction press New Entries button.

In this transaction you can configure the tax codes that will be available for end-users in FI-AP (FB60 / FB65) / FI-AR (FB70 / FB75) transactions as well as logistics invoice verification (MIRO). You can also set some tax code as default one in these transactions. Screen-shot of typical tax codes settings can be found below. Note: the visibility of input tax codes can be customized differently for FI-AP accounting and logistics invoice verification (in case, when FI-AP should be used only in certain cases that require specific tax codes). In this example the visibility of input tax codes was customized in the same way for FI-AP and MM-LIV areas.

Thus, when you access transaction FB60 you will see, that the tax code is already specified:

When end-user would like to select another tax code, the choice will be limited to transactions defined in OBZT:

Thus, there are two main benefits of the settings customized in transaction OBZT:

   1) Setting of default tax codes per accounting module (FI-AP / FI-AR / MM-LIV);

   2) Limiting the choice of tax codes to a handful of codes relevant to an area which makes it easy a) to select the appropriate tax code for end-users, and b) prevents end-users from specifying incorrect tax code (especially target tax codes instead of deferred ones).

There are some limitations of the settings in OBZT. For example, you cannot restrict the list of available tax codes for creation of purchase orders (transaction ME21N) or for generic transactions like FB01. But in most cases, especially when integrated invoicing processes are in place, FB01 will be used rarely and primarily for different adjustment postings. This transaction is also not used to manage the visibility of tax codes in SD module. Standard condition techniques in SD (VK11) ensure automatic determination of tax codes for sales documents. Condition technique determines tax codes as a rule based on the combination of tax categories in material’s and customer’s master records.

Best regards,

The Wirtschaftsmann

I have come across many documents explaining the configuration and functionality for Lock-box implementation in SAP. However I have found very little post regarding post processing aspects of Lockbox.

This document is intended to  explain the different aspects of post-processing data and assist users to successfully processing the file data. Hence I have excluded lockbox configuration part. This document is applicable only for file processed using BAI2 format

What is Lockbox post processing

Once a lockbox file is processed in SAP system through t-code FLB2 (program RFEBLB00), it is not always necessary that all the checks have successfully posted. Post-processing is required when the lockbox program is not able to automatically clear/apply all available checks in the file.

After the file processing, the the lockbox status will fall under one of following categories:

1. Applied: This status is maintained when customer is identified and all the document numbers for that customer are also identified. The program doesn’t check for amount from the file against document/invoice. It means even if amount is overpaid/underpaid in the file, the status will be ‘Applied’.
2. Partially Applied: This status is maintained when customer is identified and check has cleared one or more document numbers, but not all documents have been identified/cleared.
3. On-Account: It means that customer is identified but no document numbers have been found. Hence, the full amount of check is posted on customer account for further processing with payment advice.
4. Unprocessed: This status is maintained when neither customer could be identified through bank information nor document numbers were found, so the check remains in the un-applied payment clearing account for further processing.

How to complete post-processing of lockbox data

This activity is completed using transaction code FLB1 in SAP. Enter the input parameters in the initial screen as shown below and click on to process the checks.

In the next screen, we can see the status of all the checks, which were in the file and processed in SAP by lockbox program.

Action required for different Lockbox file status:

1. If the lockbox status is “Applied”, No further processing/action is required for reconciliation. Also, we can not find the payment advice because the system automatically deletes it.

2. If the lockbox status is “Partially Applied”, it requires further action for processing. To process the check, choose the check and then press the post button. After this step, clearing is done via standard SAP process.

3. If the lockbox status is “On-Account”, it requires further action for processing. To process, we need to change the payment advice first (highlighted above).  Select the check and then we can insert or delete clearing details. After the changes made, the advice balance should be zero.  Save the changes in advice and then post it.

4. If the lockbox status is “Unprocessed”, it requires further action for processing in the same way as that of on-account status. However, we must identify the customer in the payment advice at first before making other changes.

In this way, we can process and post all the checks in SAP system for a lockbox file.

Executive Summary

An important exercise during SAP implementation project cutover is Purchase Order (PO) migration from legacy to SAP. The legacy POs may be in various stages of processing. Some might be partially delivered while others might be partially invoiced. The scenario becomes challenging as the corresponding stock postings for such histories is already posted in legacy. While businesses would like to bring these histories into SAP they would not like to post to stock accounts or update stock quantities in the material master however they would like to post to GR/IR clearing accounts to record all open items.

This blog discusses proven SAP standard solution of open PO upload with history based on live project experiences and proposes some practical check points and processes to ensure a seamless PO history upload in SAP.

Note: Sound understanding of SAP MM-FI integration is a pre-requisite to this reading.

Business Requirements

During cutover of purchase orders from legacy to SAP businesses face challenging requirements with respect to transferring histories of the purchase orders to SAP. Legacy POs could be carrying varied PO histories as mentioned below:

 Open POs

 Partially Delivered POs (partial GR done)

 Partially Invoiced POs (Partial IR done)

In general, businesses are suggested to close all open POs in legacy and not to bring any histories along in SAP. However in some cases the PO histories become mandatory for businesses. The challenge in such cases is to bring the histories without creating any stock posting while still posting the open items in GR/IR clearing accounts along with its contra postings.

SAP Standard Solution

SAP provides standard programs to upload POs along with their histories from legacy system. It is possible to transfer open, partially delivered, and partially invoiced POs from legacy to SAP. The set of programs operate to load the PO master as a first step followed by history and item text uploads. During this process, the SAP standard automatic account determination and postings to stock and GR/IR clearing accounts based on OBYC setup is circumvented by SAP and postings are done to a user specified GR/IR clearing account (which is open for non-automatic postings) and contra accounts. Dedicated for this upload process business users need to provide the following accounts:

GR/IR Clearing Account

Contra Account Vendor Items

Contra Account Goods Receipt

The relevant accounting entries posted during cutover are as follows:

1) At the time of Inventory upload (as conducted using separate upload tool)

          Inventory account Dr

          Inventory Upload A/c Cr

2) At the time of PO History upload (using the process discussed in this whitepaper)

     a. Partial GR carry forward from legacy to SAP

         Contra Accounts GR Dr

          GR/IR clearing A/c Cr

b. Partial IR carry forward from legacy to SAP

          GR/IR clearing A/c Dr

          Contra Vendor A/c cr

3) Vendor balances upload (as conducted using separate upload tool)

          Contra vendor A/C Dr

          Vendor A/c Cr

Note that the PO history upload SAP programs do not post to stock accounts or create any material quantity updates in material masters during this upload process.

Business Benefits

 Clean open item migration from Legacy to SAP with desired PO history

 Clear Audit trail

 Standard SAP solution

Detailed Mechanism

The transfer of POs is affected via the data transfer workbench using the following programs in the sequence as presented:

The steps to be followed for the upload are as listed below:

Step 1: Create a sequential LSMW using Programs mentioned above:

As a first step Program "RM06EEI0" (upto 4.6c) and BAPI "BAPI_PO_CREATE1" (for all versions after 4.6c) are used to create PO headers in SAP. These programs are used at the time of LSMW creation as shown below:

This LSMW requires a sequential data transfer relation. PO header gets transferred first followed by PO line item in a sequential manner. Per PO header, a record of the structure MBEPOH is created and per PO item, a record of the structure MBEPOI is created. Each PO line item attaches itself with a PO header item and hence the structure relationship that gets created in LSMW is as shown below:

Note: Detailed source structure for a quick reference is available from the author over mail.

Rest of the steps of LSMW creation process remain same as any other LSMW.

Step2: Define Number Range for PO Upload- OMH6

As a best practice it is recommended to define a unique external number range for ease of identification of legacy purchase orders Vis-a-Vis purchase Orders created in SAP after go-live. Note that this is a client open activity.

Step3: Upload file to Logical Destination (SAP Application server)

The PO upload file is usually very bulky and hence need to be uploaded on the SAP application server by BASIS team for the LSMW to pick it up . SAP standard transaction CG3Z cannot be used to upload the file on application server as it has been observed that the upload files get truncated due to beyond normal file size.

Note:Sample  upload file is available from the author over mail.

  Data preparation for this upload file needs to be done with the following checks in mind.

Step4: Check Uploaded File in application Server-AL11

As a sanity check the upload file destination should be re-verified on the application server.

Step5: Display Transfer file (Optional)-OMQ5

To locate possible data errors in the upload file display the content of the sequential file in structured form using transaction OMQ5. Changes to data structure are possible at this instance.

Step6: Deactivate Statistics Update (Optional)-OM02

Deactivate the statistics updating process in order to reduce the runtime of the programs for transferring purchase orders

Step7: PO Master data Upload

Execute the LSMW created in Step 1 using the upload file on the application server.

Check that the PO headers are created in the backend but not yet released post the LSMW upload. No histories exist at this instance.

Step8: PO History Upload-SA38 (RM06EEI1)

As a next step, PO line item uploads are conducted using program RM06EEI1 as shown below:

Note:

File Name: is the application server address of the upload file that has been uploaded in step 4 

Without database update: This is for doing a test run. No documents get posted when the program is executed in this mode. It is recommended to conduct this run to check any possible errors ahead of the actual update run.

With Database update: This run updated the PO history and created accounting entries as applicable. It shows a log of the activity indicating POs loaded successfully, POs with error as well as the detailed reasons for the errors. It needs to be scheduled in the background. An upload file with approximately 6000 line items takes about 5 minutes. The SAP MM tables EKKO and EKPO tables get updated during this run.  

GL Accounts: GR/IR clearing account, Contra account for Vendor items, Contra accounts Goods receipt are GL accounts to be provided by business and to which accounting postings are expected due to the PO history upload.  

Document Types: Specify the SAP document types which are intended to be used for the above postings.

Scope of Error log: Choose "log with error message" to get detailed errors log for failed cases. Note that for POs which fail during their history upload even the PO header is not created. The POs with error can be corrected and a second upload with only the delta POs can be executed.  

Step 9: Conduct a sample data check:

Post the upload, it is recommended to check some sample POs for each detail and the accounting documents posted. For detailed check EKKO, EKPO table from MM side, Documents posted in accounts provided by business for this purpose can be analyzed.

Step 10: Deactivate ext number range for PO- OMH6

Post the upload it is mandatory to deactivate external number ranges so that the same don’t get consumed in Post go-live PO creation process.

Conclusion:

SAP’s solution for PO history upload has been used successfully in large multi-country implementations with a mandate to upload PO histories from Legacy to SAP for various business reasons. The setup for this upload is a one-time exercise with full reusability for each successive roll-out. A clear strong point of this upload process is the ability of this functionality to check errors ahead of actual database update. This gives users the ability to make corrections and allow only correct values to update SAP database.

Referenceshttp://help.sap.com

Dear all,

It gives me a privilege to share this concept, which was routed by mentor and friend who's mightier push back today couldn't have let me in working this scenario and thereby sharing with you might have delayed ages .

Thanks to my friend and mentor in this concern. Before I began further, I humbly request the moderators, mentors, excerpts and guru's to add and encourage my post in this regard. Also I strongly believe in learning and thereby ushering oneself rather focused on credibility, because more than credibility self-satisfaction and thereby open-end challenges are always waiting for enthusiasts to work on no matter what level they might achieve.

Thanks a lot in advance.....

Split Period Posting - Fiscal Year Variant (April - March)

For few companies, they might want to follow the period in a split way in a month, i.e., the client wants the business transactions to be automatically routed to the next period in the same month when their end-user posts business transactions.

Generally, by practice most of us know that in a fiscal year variant, we configure the day count of a period in every month by end date of that month, but in the above case it's little tricky, but once found it's as good as a novice game.

This is the V3 variant (April-March) Fiscal Year.

Now this is how we work for the above given scenario.......................

(1) Go to Transaction Code OB29 click on new entries or press (F5) and enter the two charactered alpha-numeric as desired (shown below) and save it to save the newly created Fiscal Year Variant.

(2) First Select the newly created fiscal year variant and the double click on the periods as highlighted (below screenshot) to define periods for the fiscal year variant.

(3) Enter the Months, Day, Period, Year Shift as shown below. [it's noticed that in the below screen shot, that we were able to enter the periods for 15th of every month, excluding december]

Explanation of the approach.....

Once the Periods are been entered as shown above, click on save button or press control+S to save it.

(4) Assign Fiscal Year Variant to the company code through the transaction code OB37, now in the fiscal year variant input field, press F4 to drop down and select the fiscal year variant(desired variant created as per the earlier step), T3, select the variant and save it further.

===================================================================================================================

>>>>>>Let us see the transaction level posting..........

(1) Document Posted on April 01st of 2015 (This is a vendor invoice)

(2) Document Posting after April 16th of 2015 [16.04.2015]

Similarly Posting for the next month, this is how it goes on......

Hope this helps aspirants, newbies and consultants to understand how the periods can be mapped as per the client's requirement to not only get the desired output further resolve such requirements.

It's not only the case of 15, but any given date of a particular month, Also to make a note to all of you before I conclude this document, here it goes, when a particular period wants to be split till 15 and rest of the periods are in tact(no change), PFA.... screenshot for your reference.

I once again, thank my mentor and my friend, whose mightier push and continuous follow-up would not have really got me a such wonderful achievement, which might feel unseemingly impossible without trying.

Thanks a lot dear members and moderators me being the part of such a wonderful community and L"earning " space too. Will see you with another recipe requirement  like this.

Have great time all.

Cheers :-)

Karthikeya

This document explains capabilities of search strings in electronic bank statement processing

Electronic Bank Statement is one of the most widely used functionality to automate bank reconciliation and related posting. It can be further optimized by use of ‘search strings’. Search strings by reading strings in “Note to Payee” can help EBS further automate functions like changing posting rule, populating values from EBS file to assignment field in accounting document, skip processing of bank code for specific house bank etc. We will see all these functionality in detail.

Passing values from EBS file to assignment field in accounting document

Once electronic bank statement is posted it becomes difficult to match accounting document with physical bank statements based on just amounts and date. Using search string we can pass specific string (e.g. reference number) from electronic file to assignment field in line item of “Wires/Check in clearing” account. This value in assignment field in line item of “Wires/Check in clearing” account can be useful in setting up automatic clearing of “Wires/Check in clearing” account. For example where receivables (Non-Lockbox) are post processed after posting of EBS (e.g. inter-company receivables), line items in clearing account can be cleared by background job for T-Code F.13.

1. Incoming Electronic Bank File (BAI format):

Electronic Bank file can be in many formats like MT940, MULTICASH, BAI etc. Shown below is one sample file in BAI format where reference number generated bank is in specific format. We want to pass reference number for each bank code in Assignment field in line item of clearing account –

g

2. Configuration of Search String -

To pass value from ‘Note to Payee’ to accounting document we need 2 search strings.

a) First one to identify the target field in accounting document for search string  and,

b) Second one to pass bank reference value in assignment field.

Search String definition-

For configuration follow path - SPRO > Financial Accounting (New) > Bank Accounting > Business Transactions > Payment Transactions > Electronic Bank Statement > Define Search String for Electronic Bank Statement.

Configuration of first search string (BANK REF. IDENTIFIER) to identify the target field in accounting document:

Please note that there is no mapping for this search string as it is only used to identify the target field in accounting document. In our example in BAI file bank reference comes in format “IA123456789012” or IA1234567O9012 where first 2 characters are constant (IA) followed by 12 numeric values where 8^th character can be alphabet “O” or a number. In SAP performance assistant you can see how to configure search strings. I have configured search string as follows:

• First 2 characters I and A as constant.
• Next 7 characters as numbers. Numbers in search strings are identified by sign ‘#’.
• 8^th character as (#|O), which means 8^th character can be an alphabet ‘O’ or a number. System will identify string in both the cases.
• Last 4 characters as numbers.

For different banks format of reference value can be different. However, it should have some unique identification like in our example it starts with ‘IA’, so that system can uniquely identify the string.

Configuration of second search string (BANK REF. POSTING) to pass bank reference value to assignment field –

Please note that here I have configured search string exactly as the first one but it has mapping. If search string has mapping it means that value will be passed to accounting document.

Search String Use-

Search strings are assigned to combination of Company Code/House Bank/Acct ID/Bank Code. To pass value to specific field in accounting document we will use BDC Fields.

BDC fields work as follows (Excerpt from SAP Performance Assistant) –

The BDC fields are a means of filling screen fields if there is no suitable target field in the bank data store. You must know the technical name of the relevant screen field (if you do not know it, use the F1 help to find it out).For example, if you want to transfer a control indicator in the event that the key word "TELECOM" appears in the note to payee, you can proceed as follows:

Use the search string TELECOM with mapping "       " (all blanks) for the three target fields "BDC Field Value 1", "BDC Field Name 1" and "BDC Account Type 1". The constants to be entered in the individual BDC fields are always stored in the "Mapping Basis" field:

BDC Field Value 1 = "V1"

BDC Field Name 1 = "BSEG-MWSKZ"

BDC Account Type 1 = "0"

If you want to transfer the content of only one particular line, you can use the "BDC Account Type" field to control the process. If you enter the constants 0, 1, 2, or 3 in this field, the transfer only takes place as specified. The constants here mean the following:

0: First line, posting area 1

1: First line, posting area 2

2: Second line, posting area 1

3: Second line, posting area 2

If you do not control the transfer in this way, the system tries to transfer the screen field defined under "Field Name" in all the posting lines in posting areas 1 and 2. This cause an error on the grounds that the field does not exist (for example, because a control indicator for a particular account does not accept input.

In the control indicator example, note that you must set the "Calculate Tax" indicator too, so that the posting can be made automatically. You then need the following settings in addition:

BDC Field Name 2 = "BKPF-XMWST"

BDC Field Value 2 = "X"

BDC Account Type 2 = "0"

Continuing to our configuration proceed as follows-

1. For relevant Co Cd/House Bank/Acct ID/Bank Code combination assign first search string (BANK REF. IDENTIFIER) to “Target Fields” “BDC Field Name 1” and “BDC Account Type 1”.

2. For same combination in step 1 assign second search string (BANK REF. POSTING) with target field “BDC Field Value 1”.

3. Assign following values to fields “Mapping Prefix”:

BDC Field Name 1                 - BSEG-ZUONR (Target field)

BDC Account Type 1             - 2 (Target line)

BDC Field Value 1                 - IA000000000000 (Target value)

Once above configuration is ready, for that specific Company Code/House Bank/Acct ID/Bank Code system will read any search string with format IA############ or IA########O#### and pass that value to assignment field of clearing account. Of course you will have to configure your search string according to your requirements.

3.  Changing the posting rule for same bank code:

It may be possible that a bank code is posting to specific set of GL accounts via a posting rule; however we want to change GL account posting for the same bank code. It may be possible for example bank uses same code for ACH OUT and ACH RETURN. We will want system ACH OUT to post by debiting ACH OUT account and crediting Main Bank Account. However when there is ACH return we want to reverse the posting. In case bank uses same bank code however in note to payee gives information in the form of string “ACH RETURN”, we can configure a search string to identify such returns and change the posting rule for reversal. Example:

Bank Code for ACH OUT – 169

Posting rule for ACH OUT - WF08; debits ACH clearing account, credits bank account

Posting rule for ACH RETURN – WF10; debits bank account, credits ACH clearing account,

BAI file comes as shown below for ACH out –

BAI file comes as shown below for ACH return –

For ACH out posting would have been gone through posting rule WF08 which is configured as shown below –

We want to substitute posting rule WF08 with posting rule WF10 for bank code 169 if note to payee has string “ACH RETURN”. For ACH RETURN search string can be defined as shown below –

Assign search string configured above in node “Search String Use” as follows:

Assign search string “ACH RETURN” to relevant Company Code/House Bank/Acct ID/Bank Code combination. Select target field as “Posting Rule”. Assign “Mapping Prefix” as WF00. When substituting posting rule WF08, system will take “WF” from mapping prefix and “10” from search string definition. Mapping prefix works as follows (Excerpt from SAP help) –

A string of characters you can define yourself to have the funds center found "filled out" in the event of a successful search if it is too short.

The prefix should be the same length as the document numbers being searched for in the system. The later part is then replaced with the search string found.

If a "hit" is longer than, or as long as, the relevant prefix, the hit overwrites the whole prefix.

Use

This function is particularly useful for filling in redundant parts (such as leading zeros) when the reference information is incomplete.

Example

Prefix "1800000000" and hit "12345" results in number "1800012345".

Once above configuration is in place any file with bank code 169 assigned for house bank and account when loaded with string ACH RETURN will replace the posting rule WF08 with WF10.

This document explains the purpose of maintaining "Vendor Number Ranges" while maintaining parameters in F110 in the "Additional Log" tab and the difference it can make if the same is not maintained.

SAP FI supporting team receives few tickets on Automatic Payment program (SAP Transaction Code-F110), reporting that there are few invoice line items in the Payment Proposal falls into exception with error codes (for e.g. 001,003,006,007,16 & 98). There are nearly 63 error codes defined in SAP, and the error codes 007 is very generic and difficult to identify the reason for those invoice line items that falls into exception.  The error message instructs to refer to the job log, but still the log messages are very deceptive.

What is missing?

When the BU/user executes Automatic Payment Program, usually the parameters/options in the “Additional log” section were ignored, because users were not trained to understand the benefit of maintaining the parameters in the “Additional log” section.

Case 1: When Vendor number range in Additional Log tab is not maintained

Case 2: When Vendor number range in Additional Log tab is maintained

If the “Vendor Number ranges” are not maintained in the F110 “Additional Log” section,

1. Affects Consultants Productivity- When the “Vendor Number Ranges” are not maintained in the F110 Additional Log section and if particular invoice line items is missing some information as per the configuration in SAP, then the system throws the error messages and 007 is not very clear. Once the ticket is assigned to the respective FICO Consultant, then the same scenario needs to be replicated in the Quality system. Sometimes the same vendor and related master data settings will be missing in Quality. In such cases, Consultants need to create a similar vendor with the same settings as in Production system and replicate the invoice line items. It may consume much time depends on the source of invoice/Down Payment Request (e.g. whether the invoice/down payment requests are received from core FI module or through MM Module via Purchase Orders).
2. User’s knowledge is not enhanced- If the users were trained to maintain the “Vendor Number Ranges” in the F110 transaction, then the error can be corrected by the user, unless if there is any configuration/setting is required in IMG.

Proposed Solution:

The “Vendor Number Ranges” in the F110 “Additional Log” field to be made mandatory, so that BU/User cannot create the Proposal and the system throws the error message, instructing to maintain “Vendor Number Ranges”.

Dear colleagues ,

i have explained below simple steps to create validation on Groups of center with group of cost element .

wishing it helpful

1. Split The Cost elements and cost centers you have to Groups

Cost element Group :- MFG Cost Elements / MRK Cost Elelemtns

Cost Centers Group :-Manufacturing Cost Centers /Marketing Cost Centers  

1. Create Set table By T_CODE   GS01 for Each group

1. Create Validation on the mentioned Combination  .  GGB0

Just I have create Set table for all cost element to execute validation only for cost elements

1. Activate Validation  .  OB28  

       I hope that I have Delivered clearly my solution

Regards

Emad Gamal

Background processing of Dunning-

Dunning can be processed automatically in background which can be scheduled daily,monthly,weekly or yearly.
SAP provides a standard program RF150SMS which can be used to schedule Dunning run.
The steps to be followed are :

1.) Create a template in F150 specifying all the details i.e.  Run Date, ID, Company Code and Customer numbers, Documents posted upto and Dunning Date and save it without scheduling.

2.) Call program RF150SMS furnishing the details same as mentioned in F150 template also checkbox on field Copy Parameters and dynamic target date calculation as the date same as program run date.. Checkbox on With Dunning Printout with printer name as LP01.

3.) Save the program variant with suitable name and description, checkbox on Only for background processing. In Dynamic Target Date Calculation use Selection Variant as D- Dynamic Date Calculation and Name of the variable as Current Date (you can also use another mentioned in the inputs given according to your requirement).

4.) Again Call RF150SMS, click on Background tab and call the saved variant.

5.) Click on Schedule Tab Enter Job name,Start date and Time from which and on which you want to schedule it periodically then click on schedule periodically and use the required period interval lets take as Days (for daily processing) and fill the number of days. Click on Tick.

The Dunning gets scheduled for daily job.

Job status can be checked in SM37.

This article deals with the significance of the field 'On Account Posting Key' in Electronic Bank Statement. Although this is a very small and simple configuration in Electronic Bank Statement, it has significant implications in terms of the handling the way in which postings are made during the Upload of an Electronic Bank Statement.

The configuration for the same is maintained in the below setting:

Financial Accounting-Bank Accounting-Business Transactions- Payment Transactions- Electronic Bank Statement- Make Global Settings for Electronic Bank Statement.

A screenshot of the configuration for the same is given below-

The on account posting key is maintained in the dialog box ' Define Posting Rules':

The 'on account posting key' is primarily used in those cases where an Interpretation Algorithm is assigned to an External Transaction code.  The 'on account posting key' will be maintained against the posting rule defined for the Corresponding External Transaction Code that uses the Interpretation Algorithm.

Just to explain the above point with an example, the external transaction code NCOL uses Interpretation Algorithm 015:

So for the posting rule COL+ and RTI-(mapped to External Transaction code NCOL), we would maintain an 'On Account Posting rule' as shown below:

Detailed Explanation:

When an Interpretation Algorithm is mapped to an External Transaction Code, system expects an existing document in the system which would be cleared. However there might be cases when the document which has to be cleared does not exist in the system due to delay in posting or any other reason. In  such cases the 'On Account Posting key' is used.

When such a document(document to be cleared) is not found the system would still do a posting (but without clearing) with the Posting keys maintained in this column. This feature is very useful as it enables posting even when there is no corresponding document which has to be cleared. If not for this feature, the system would not do any posting as the logic works only on Post with Clearing basis and  the balance as per the Bank Statements would not have tallied with the main Bank Account (G/L), always leading to mismatch and bringing up the need for Reconciliation to tie the Main Bank account with the Bank Statement.

With this setup -when no document is found to be cleared, then system would post still post a document without clearing
using the ‘on account posting key’ maintained against the Posting Rule.

The concept of on account posting is explained with the help of an example below:

When a file is uploaded and system does not find any document to be cleared (even though the transaction code has an interpretation
algorithm and expects to find a document to be cleared) then the on account posting key will be used to make the FI posting.

In this case, the posting log after loading the bank statement will appear as below:

When FEBAN is accessed for that particular Bank Statement it looks as below:

Documents which are posted 'on account' will appear in yellow as shown above. This means document has been posted without clearing.
The document number posted will appear against the ‘PmtAcc’ Document as shown above.

Such documents which could not have been cleared will have to be cleared manually subsequently.

The document number for all normal postings which are cleared or which do not require clearing (when no Interpretation Algorithm is assigned to the Posting rule) will still appear under
 
An example of the FEBAN screen when a file which has been loaded  successfully cleared is shown below:

Documents which are posted with clearing will appear in green as shown above. This means document has been posted with clearing.
The document number posted will appear against the Document as shown above.

Thus we see that with the help of 'On Account Posting key' we can ensure that all postings are made to SAP even if system is not able to find a corresponding document to clear. This will ensure that the main account balance ties to the balance in the Bank statement(unless there is some configuration missing).

Introduction to Debugging

SAP consists for various transactions codes and data. Data are stored in the tables and the transaction codes have ABAP programs at the back end. Literal meaning of debugging is ,to make something(a program in current discussion) bug-free. But that is just one aspect of debugging.

Through debugging, we can analyze a program, understand the flow logic and most importantly find out the root cause to any issue .Although Debugging is the obvious task of an ABAP consultant, the debugging knowledge would be of great help to functional consultants. It will save their time for analysis and issue resolution , reduce over-dependence of ABAP team , help in effort estimation.

Let's look at the different aspects of debugging. We will divide the discussion in to the below parts.

1. Programs in SAP ABAP

2. Initiating the Debugging

3. Breakpoints

4. General tips

1. Programs in SAP ABAP

As functional consultants, we deal with many transaction codes and behind each transaction code, there is a ABAP source code. It can be either SAP delivered or customized code, written by ABAP consultant for specific need.

When we execute the program, the control runs through the program and delivers the output. When we debug, the control remains in our hand and runs through the program line by line, thereby allowing us to find out a specific bug, or clarity about a specific logic.

2. Initiating the Debugging

Debugging can be initiated in two ways.

a. Using /h command and executing the transaction.

b. Putting a break-point, at a particular line of the program and executing

the transaction.

As functional consultants , we would be mostly using the 1st option. The 2nd option is used, generally by ABAPers, where they want to see the behavior of a particular section of the code. Let's see examples of each of the above mentioned methods.

Example

a. Using /h command and executing the transactions

Below is the initial screen of a transaction.

First step is to use the command '/h'.

A message will be displayed in the bottom of the screen.

The resulting Screen will be as below.

We can see the current control with the yellow arrow.

• As we press ‘F5’, the control proceeds further.
• If we press F8, two things can happen

          1. If any Break-point is there, the control will directly flow there.(Break-Points have been discussed in more detailed way in coming slides)

          2. If no break-point is there, the debugging will end and the program will get executed.

• As we move along the program, we may encounter, Subroutines/function modules, which are nothing but a piece of code within the program, which take inputs and provide a specific output.
• If we Keep pressing on F5, we will go inside the Subroutines/function modules and go through each line.
• If we have yet not entered Subroutines/function modules , then by pressing F6 , we will skip going through the code piece and the Subroutines/function module will be completely executed.
• If we have entered Subroutines/function modules , then by pressing F7 , we will come out of the code piece and the Subroutines/function module will be completely executed.

b. Putting a break-point, at a particular line of the program and executing the transaction

This can be done by going in to the source code editor (SE38/37 etc.) and putting the break point at the desired line. Cursor can be put on the particular line , at which we need the control to stop and click on the break point button(highlighted in the below screenshot).This will create the breakpoint in the program.

When we execute the program, the control will go to that point and stop.

3. Break-Points

Break-point is the point where the Program execution comes to a halt and from there on we can continue debugging or straight away execute the program , by pressing F8.

There are various ways, through which we can put a break-point in a program . Two mostly used ways are as below.

1. During Debugging the program

2. Before Debugging/Executing the program

Lets discuss about each of the ways.

1. During Debugging of the program

During debugging break point can be put in two ways.

a. Jumping to a specific processing block

This is one of the important methods and by far the most useful for functional consultants.

Generally we tend to debug, when we encounter an error message. In that case, we can put the breakpoint, exactly at the point , where the error originated. And once we execute the program, that will take us straight to that point.

Let's take an example of the current program. It takes the input as an AL11 path. The path must be a valid one. If we put an invalid one, it would ideally end in error. Suppose We encounter such an error, while executing the transaction in question.

Above is the initial screen and upon execution, we got the below error.

1st thing to do after this is double clicking the error message which will give us the message class and the message number In the screen below AD is the message class and 010 is the message number and the message, being in red, indicates that it's an error message.

We start the debugging, by using /h and then, we put this message class and number in the debugging screen as mentioned in the following screenshot.

Now executing the program(F8) will take us to the exact point of error, where we can analyze the reason of the error. In this specific case, the IF statement below says, if the 1st two characters (OFILE_SAVE+0(2)) is not '\\', then issue an error. The input that we provided in the selection screen started with '//' , and hence it resulted in error. That's how, we find out the reason of an error, in this method.

b. Using the stop icon, during debugging

Once the debugging screen appears, breakpoint can be put by using the highlighted breakpoint option.

2. Before Debugging/Executing the program

This can be done by putting a breakpoint in the source code editor (SE38/37 etc.). When we execute the program, the control will go to that point and stop.

In SE38, Cursor can be put on the particular line , at which we need the control to stop and click on the break point button(highlighted in the below screenshot).

Next when we execute the program or transaction, the control stops at this point.

4. General Tips:

Given below are some general tips, suggestions and terminologies involved in debugging.

• Debugging with the new Debugger Opens a new session. Hence , before debugging, ensure that we have enough room for the same, else, automatically the old debugger opens.
• During Debugging, if at any point, we want to see the source-code, we can do so in the following way.

• During debugging, we come across select statements, which are nothing but the statements, which fetch data from database table and store in the internal table in the run-time. If we click on the table icon(highlighted in the below screenshot) , It opens up the table in the next window. We can download the table data in an excel format for our analysis.

Below are few important parameters and terminologies with respect to debugging.

• SY-SUBRC : It's an indicator, that shows , whether the execution of a “Select statement” , “Function Module”, “Subroutine” , “Method”, is successful or not. When sy-subrc is 0, it indicates that the execution is successful.
• Variable : It’s a temporary storage parameter, that holds a value during the program run-time.
• Constant: As the name suggests, it holds a constant value, which is hard-coded in the program.
• Tables : When the control passes through a select statement, up on successful execution, the table(internal table) gets filled in the run-time.
• Structures : Structure is different than a table. Its just a template, but not a table.

These were some basic information, which can be handy to the functional consultants. Debugging has far more aspects and we can explore more of them, as we continue to be involved in more of debugging. Your comments and suggestions are most welcome.

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

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

There are three Options to configure the E-Bilanz in SAP:

• Option 1: SAP ERP/Other Systems with SAP BusinessObjects Disclosure Management
• Option 2: SAP ERP with SAP ERP Client for E-Bilanz
• Option 3: SAP ERP with a non-SAP-Software (for Example DATEV)

I will show you the configuration of the simplest of this three Methode (Option 3), because a lot of companies in Germany use together with SAP the non-SAP-Software DATEV.

Step 1:

Download the actual taxonomy from homepage http://www.esteuer.de from Bundesfinanzministerium. The ZIP-File contains several files. Important: don't unpack this ZIP-File! Read SAP-Note 1690315. This note informs which one of the files is the leading file for the upload.

Step 2:

Go to transaction FSE1_XBRL and upload the (unpacked) ZIP-File:

In the next screen choose the leading file (look at SAP-Note 1690315):

For taxonomy 5.3 choose the marked file:

Confirm the button.

You will receive the message "Version EBIL was loaded successfully".

Step 3:

Go to Financial Accounting (New) --> General Ledger Accounting (New) --> Periodic Processing --> Document --> Define Financial Statement Versions (Electronic Financial Statement).

Click the button "Financial Statement Items"

You have to assign in this step all your accounts to a position of the taxonomy.

Step 4:

After all accounts are assigned to a taxonomy position you can show with transaction FSE0_XBRL the financial statement in XBRL taxonomy form.

Step 5:

With transaction code FSE0_EXPORT_NODES you are able to export the XBRL-Statement to Microsoft Excel.

Step 6:

Upload the Excel-File with the XBRL-Statement to DATEV.

When you do this upload to DATEV  for the first time, there are perhaps a lot of errors, which you have to correct then in SAP. Only when the upload to DATEV has no errors, the sending of the electronic financial statement from DATEV to the finance office will be possible.

There is also a possibility to load the global common datas (GCD) in SAP. I will post this in a second document.

Hello SAP Financials Community,

Good day to all of you!!

This document is in continuation to my previous blog on Simple Finance.

In this document, I will make an attempt to summarize the features / changes introduced by Simple Finance Add-on 1.0, for various process areas / activities.

Lets hit the ground now!!

The below summary is prepared out of document published by SAP, however, in a concise and easy-to-remember form. I have myself explored a majority of these, but not all.

Hope you enjoyed the learning. Keep watching this space for other documents in the series

Do share your feedback about the document, once you read it. You may leave your comments at the end of the document, by clicking on "Add Comment"

You may also forward it to your colleagues so that it reaches the maximum audience

Best Regards,

Ajay Maheshwari

PS: Tagging SAP ERP Financials - Controlling and SAP ERP Financials  - Asset Accounting forums into the document

The target of this document is to post the impairment of assets, under the IAS 36 standar, in SAP ECC 6 and reflecting this values in FI-AA module.

First of all, you have to activate the bussines function FIN_GL_CI_3. You can do this in transaction SFW5.

Customizing

New transaction types:

• Transaction type for impairment rule IAS 36 (debit) for current year (transaction type group A2)
• Transaction type for impairment rule IAS 36 (debit) for prior year (transaction type group A1)
• Transaction type for impairment rule IAS 36 (credit) for current year (transaction type group A2)
• Transaction type for impairment rule IAS 36 (credit) for prior year (transaction type group A1)

For each depreciation area, a flag may be recorded both to devalue / revalue the acquisition price and production costs, as to devalue / revalue depreciation:

To post the impairment, should be marked for each depreciation area of assessment impairments are taken into account in the implementation of accounting for depreciation:

In addition, the accounts must be assigned to use the impairment:

Other issues:

If you want to separate in a report the impairments and the reverse charges of impairments, you should separate by transaction type in the asset history sheet. The customizing in this case is:

If you have posted investiments grants, the run of the impairment report don’t have a retirement of this grants. You should do this retirement manually by the standar retirement transaction.

Implementing Badi FIAA_IMPAIRMENT_DISTR_CUST

If the distribution of impairment is different in each asset, you can use the Badi FIAA_IMPAIRMENT_DISTR_CUST to do a specific distribution for your requirements.

For this, you can create an implementation in transaction SE19:

You need to create a class ZCL_FIAA_IMPAIRMENT_DISTR_CUST assigned to this implementation to include the ABAP code to do the distribution.

Purpose

I would like to provide a document that outlines the basics of SAP tax configuration and provides a couple of examples of how tax code could be determined in SD and MM.

Overview

• SAP provides the majority of the tax configuration out of the box by country
• There are three SAP areas that work together to determine taxes FI,MM, and SD

  FI – Base configuration for tax procedures, rates and accounts

  SD – Configuration/master data to determine output tax code

  MM – Configuration/master data to determine input tax code

• Master data such as customer, vendor, and material, as well as transactional data like POs and Sales Orders are key to determining the correct tax
• Rates can be maintained in SAP or SAP can call an external system for them (this document with focus on rates maintained in SAP)

FI Tax Basics

• Tax configuration is done by country
• All company codes in the country share those settings
• Two Main Components:
  • Tax Calculation Procedure – Provide the method of calculation – normally use SAP standard
  • Tax Codes – Provide the rates

Tax Procedure

• These are provided by SAP for each country – General recommendation is to use delivered logic
• Tax Procedure, related conditions, and access sequences can be viewed in transaction SPRO at the path Financial Accounting Global Settings>Tax on sales/Purchases>Basic Settings>Check Calculation Procedure

Tax Procedure Example

• Steps define calculation, conditions, and account assignments

Condition Type Example

• Condition record defines access sequence, and other characteristics about the condition

Access Sequence Example    

• Access Sequence defines field required to access a condition
• For example to find a condition for the entry below the system will use Country, Tax Code, and Tax Jurisdiction

Configuration - Assign Tax Procedure to Country

• Tax Procedures are assigned to countries in transaction OBBG

Tax Jurisdictions

• Represent government authorities to which taxes need to be paid
• SAP allows up to 4 levels tax jurisdictions representing state, country, city, and others

Configuration - Jurisdiction Code Structure

• Tax Jurisdiction structure must be defined in transaction OBCO

Configuration - Maintain Jurisdiction Codes

• Jurisdiction codes are maintained manually in transaction OBCP for tax procedures that do not use an external system

Tax Codes

• Tax Codes are maintained by country and jurisdiction code
• They define the rate that is used in calculation
• They are maintained in transaction FTXP
• Don’t be confused on the name, this transaction can create,maintain, and display tax codes

Tax Code - Properties

• The properties of the tax code identify its code, name,  type (input vs output) and other information about it

Tax Code - Tax Rates

• In the tax rate screen you enter the appropriate tax rates
• You can also see the account assignment key and the conditions that are used to calculate a value in the follow on transactions such as SD invoice

Tax Account Determination

• Accounts are assigned in transaction OB40
• You can also see the account assignment key and the conditions that are used to calculate a value in the follow on transactions such as SD invoice

Tax Code Determination

• At the end of the day the tax is determined based on the tax code and the tax procedure on the AP or SD invoice
• SAP multiple ways to determine the tax code, condition tables, master data, programs, manual entry, etc.
• Method can be different by situation
• This document shows an example of how a tax code could be determined for an SD invoice (output tax) and SRM Pos/invoices (input tax)