USG Billing Errors Management VF04 VFX3 VOEX SAPERP

Billing Errors Management
VF04 / VFX3 / VOEX / V.21
Date: 18-May-2021
Billing Errors Management VF04 / VFX3 / VOEX / V.21
Page 1 of 48
Review Frequency: 2 Years Security Level: RB Internal
Contents
1. INTRODUCTION....................................................................................................................................... 3
1.1 Purpose.......................................................................................................................................... 3
1.2 Process description and scope....................................................................................................... 3
1.3 References..................................................................................................................................... 3
2. INSTRUCTIONS........................................................................................................................................ 4
2.1 VF04 Maintain Billing due List Report.................................................................................................... 4
2.1.1 running the billing due list for markets billing on PGI (post goods issue)..........................................5
2.1.2 running the billing due list for markets billing on expected POD (ePOD) or actual POD.............6
2.2 Identification of VF04 errors and resolution........................................................................................... 8
Blocked for Billing.................................................................................................................................... 10
Proof of Delivery (POD).......................................................................................................................... 13
Pricing Issues.......................................................................................................................................... 14
Material Master data issue...................................................................................................................... 19
User Status FIAR block........................................................................................................................... 19
2.3 VFX3 Release Billing Documents for Accounting Report (No accounting document created).............21
2.2.1 Identification of VFX3 errors and resolution...................................................................................23
Pricing error............................................................................................................................................. 24
FI/CO Interface errors (accounting interface error).................................................................................27
Invalid Tax code...................................................................................................................................... 30
Account determination error (accounting block)......................................................................................31
Foreign trade data error.......................................................................................................................... 34
Error in authorization............................................................................................................................... 41
2.4 V.21 log of collective run – alternative to running VF04 and VFX3...............................................42
2.5 VOEX Foreign Trade: Operative Cockpit: Export Billing Documents...................................................44
3 REPORTS................................................................................................................................................... 48
4 APPROVAL................................................................................................................................................. 48
5 UPDATES................................................................................................................................................... 48
Date: 18-May-2021
Page 2 of 48
1. Introduction
1.1 Purpose
The purpose of this user guide is to describe processes necessary to manage blocks and errors that are
captured in VF04 report (Billing Due List), VFX3 report (Blocked for Billing Documents) and VOEX (Export
Billing Documents) report and preventing the system/user from the complete billing.
The aim is to ensure that users responsible for dealing with VF04 and VFX3 errors are able to identify
appropriate steps and follow agreed processes whilst releasing billing blocks and resolving failures.
1.2 Process description and scope
This document applies to all Customer Service team members responsible for performing billing activities. It
provides information on how to produce VF04 and VFX3 reports and how to deal with the most frequent
billing issues.
Audience:
 Customer Service team
1.3 References
This document has been written with reference to the documents listed below:
Reference No Description Where Held
GLOIS_SAPERP_URS_SD18 Billing Process for 3rd Party Customers Solman
GLOBP_SAPERP_SOP_SD2 Gearbox
Billing Process 3rd Party Commercial
0
Date: 18-May-2021
Page 3 of 48
2. Instructions
2.1 VF04 Maintain Billing due List Report
This report should be run to identify billing documents that have not been created by the automatic Billing
Job. Billing due list functionality allows the user to process billing documents in batches.
The system creates a list of sales documents to be billed using the selection criteria.
The billing due list can be displayed prior to processing so the user can choose the documents to be
invoiced. When the user processes the billing due list, the system creates the corresponding invoices for the
selected documents.
The transaction code VF04 displays all documents due to be invoiced.
Each sales order type entered in the system should trigger a billing document. If errors occur and the billing
document is pending, the transaction will display in VF04 report.
Possible types of errors include the following examples:

1) Billing blocks
2) POD error (for markets who bill using actual POD or expected POD)
3) Pricing error
4) Material Master data error
5) User Status FIAR blocks
It is especially important to complete the review in VF04 daily and before each period end and ensure
exceptions are investigated and resolved.
Run this transaction daily after the billing job.
Date: 18-May-2021
Page 4 of 48
2.1.1 running the billing due list for markets billing on PGI (post goods issue)
1. Enter transaction code VF04 in the command field and click (Enter).
2. In the Billing Data section leave a Billing Date from blank.

If you are running VF04 after your billing batch job on the same day, insert today’s date in the “to” field.
If you are running VF04 the day after the last billing batch job, enter the previous day’s date into the
billing date “to” field. If you were to put today’s date and that your billing batch job has not run today yet,
you will display documents due to be billed today (not processed by the billing job yet).
3. Input the relevant code in the Sales Organization field of the Organizat. Data section
4. Input “00” in the fields: Distribution Channel and Division
5. In the Documents to be selected section tick all that apply to your billing process. Normally, Order-
related (for credit / debit memos), Delivery-related (for 3rd party invoices and return credit memos) and
Intercompany Billing (if applicable) are ticked.
6. Click Execute (F8) to run the report
Date: 18-May-2021
Page 5 of 48
7. Extract the VF04 report to Excel if you want to keep the daily log to see how many days a particular
document has been held (recommended from KPI point of view).
8. Select all items.

9. Right click on the grey button and choose Spreadsheet, then select a formal of your file.
10. Save the file in the desired location.
2.1.2 running the billing due list for markets billing on expected POD (ePOD) or actual POD
1. Enter transaction code VF04 in the command field and click (Enter).
2. In the Billing Data section:
- Leave the “Billing Date from” blank.
- Regarding the “billing date to” field, it is important to note that the billing date in VF04 always
reflects the PGI date, even for markets or customers who are POD relevant (billed following the
expected or actual POD process).
Even if your market bills on POD, you will still have a few exception customers which are billed
on PGI (for example sample customers). Therefore, you need to populate either today’s date in
the “to” field if you are running VF04 straight after your billing job, or yesterday’s date if you are
running it in the morning of the following day before the first billing job. If you don’t populate the
“to” date you will have documents displayed in the billing due list which are not due for billing yet
(as their billing date is later in the future).
4. Input “00” in the fields: Distribution Channel and Division
5. In the Documents to be selected section tick all that apply to your billing process. Normally, Order-
related (for credit / debit memos), Delivery-related (for 3rd party invoices and return credit memos)
and Intercompany Billing (if applicable) are ticked.
You will also tick “Doc with POD status” so that only documents which are “not relevant for POD”
(such as credit, debits, returns) or which have the POD status 'C' which means the POD has been
confirmed are selected.
Date: 18-May-2021
Page 6 of 48
You can then extract and save the report in Excel if you want (please see the steps in the previous point as
they are identical)
Analysing the results:
Once the report is run, you should NOT have any document with POD status C.
If you do have documents with POD status C (which means the POD has been confirmed but the
document has not been billed):
- wait until the next billing batch job has been done, in case the POD confirmation was done after
the previous billing batch job. It has been made very clear that for markets who use expected
POD or actual POD, the customer service team must not bill any document manually. This will
be closely monitored by the finance teams.
- If the document has still not been billed automatically after the following batch job, please
contact your local finance and customer service manager to get their approval to bill the
document manually. When you try to bill the document manually, you will get an error log that
will indicate what is the error preventing billing.
Note: remember that even for POD relevant documents which are either billed on planned delivery date for
expected POD or on actual delivery date for actual POD, the “billing date” in VF04 still reflects the PGI date.
Therefore don’t be alarmed if you see a document with a POD status C and a billing date many days in the
past – this could simply be because the transit time is very long, and therefore the actual or planned delivery
date is several days after the PGI.
Documents with POD status “blank”,

These documents are not relevant for POD. This can either be customers which are approved exceptions to
the POD process, but also credit, debits and returns which are not relevant for POD by nature.
- For these documents, wait until the next billing batch job has been done, in case the PGI or the
finance approval was done after the last billing batch job for example.
Date: 18-May-2021
Page 7 of 48
- If the document has still not been billed automatically after the following batch job, try to bill the
document manually, you will get an error log that will indicate what is the error preventing billing.
2.2 Identification of VF04 errors and resolution
The identification and resolution of billing errors will be done in the same way, regardless if the market is
billing on PGI, expected POD or actual POD.
Every line in the VF04 report must be investigated and the reason of error must be identified by the
Customer Service Analyst and resolved appropriately.
You can either release all documents at the same time or process one document only.
11. To bill all documents select them all and click on or .

The difference between the two is that the "Collective billing" button will execute the billing in the
background for the selected documents and you cannot change anything.
However, the "Online collective billing" button means you have access to the collective billing document
before it is created, and you can change certain data.
12. To bill one document select it and click on
Once document(s) has been processed you will see whether the billing occurred or whether there are any
errors that prevent the user from the billing (in this case you will see in the Processing Status column).
In case of errors review the error log, investigate the nature of the issue and follow up with the right team to
resolve it immediately (or resolve yourself if you have the right access to do so).
Date: 18-May-2021
Page 8 of 48
13. Click on the error log
You will see the list of error(s) encountered in the given document.
Date: 18-May-2021
Page 9 of 48
15. Click on to see the technical details of the error.
You will be able to check in which schedule line number the error has taken place and take necessary
actions to resolve it.
Blocked for Billing
Blocked for Billing errors need to be resolved by the Customer Service team. There is no dependency here.
1. Double click Error Log or search in VL03N transaction to open outbound delivery document (Delivery
document = “Document” column in VF04 report).
2. Click on the Document flow
Date: 18-May-2021
Page 10 of 48
3. Click on the Standard Order and then Display Document icon
4. Check if the Temporary Block in Billing block field is set up.
5. Click on Doc.header details .
6. In the sales order header data check who created the order (SAP User Id) in Created by field.
Contact the person and request the block to be removed in VA02 transaction or remove it yourself.
Date: 18-May-2021
Page 11 of 48
7. Go to Sales Document and click Change. This will take you to VA02 transaction.
8. Go do dropdown list in Billing block field and select the blank line .
9. Save the sales order .
Date: 18-May-2021
Page 12 of 48
Your order has been changed and saved.
Proof of Delivery (POD)
POD error in VF04 report means that the 3 rd party invoice can be billed to the final customer only after
receiving a Proof of Delivery confirmation that the shipment has been delivered. This applies to markets that
follow POD billing. POD errors need to be resolved by the Customer Service team but the POD confirmation
must be done by Logistics/3PL.
Date: 18-May-2021
Page 13 of 48
The resolution is to wait until POD is confirmed and then bill the Outbound Delivery via VF01 transaction or
release from the VF04 Billing Due list.
Pricing Issues
Pricing errors might be quite common. In order to bill the outbound delivery document the pricing master
must be correctly maintained.
1. Go to Edit and select Log.
Date: 18-May-2021
Page 14 of 48
2. Review the technical information and copy the sales order number.
For pricing errors in VF04, the Customer Service analyst opens the sales order in VA03 transaction and
identifies line items with a missing pricing condition by checking the Incompletion Log.
3. Go to Edit and select Incompletion log.
Date: 18-May-2021
Page 15 of 48
4. Check which line items encountered the pricing issue. In our example it is item 10 and 11.
Customer Service Analyst then checks the pricing condition of the particular line item.
5. Highlight the item line and click on Item conditions .
Date: 18-May-2021
Page 16 of 48
6. Click on Analysis.
The Analysis Pricing tab provides all details about pricing conditions and which ones are missing. The
Customer Service team cannot solve pricing queries hence you will need to contact the team who is in
charge of the Pricing Master.
Date: 18-May-2021
Page 17 of 48
7. Go to details of the pricing condition that has caused the billing error
8. Review which price is missing and contact relevant team
After the price is loaded, the sales order needs to be updated with the new price and billing document
triggered from VF04 (highlight the line on the VF04 > Individual Billing Document > Save).
Date: 18-May-2021
Page 18 of 48
Material Master data issue
When any order or outbound delivery document is stuck in VF04 due to Material data the Customer Service
Analyst will need to contact the data steward (or whomever the task of the material master maintenance has
been assigned to) to set up the data properly.
One example of the material issues is the message saying “Material data not fully maintained in the sales
org…”.
User Status FIAR block
For order-related documents such as credit memos, debit memos and invoice corrections there is a
configuration set up which blocks them from billing unless the finance approval has been provided. The block
is called “User Status FIAR”.
The error message will show below details.
Date: 18-May-2021
Page 19 of 48
The resolution of this error sits within AR functional area (release from the transaction V.26).
Date: 18-May-2021
Page 20 of 48
2.3 VFX3 Release Billing Documents for Accounting Report (No accounting document created)
This report should be run to identify any billing documents that have been created in the system, however
the financial accounting entries for the bill have not been created in the system. This is usually because there
is some missing data. The system posts invoices to Accounts Receivable (FI module) automatically as soon
as they are created in the SD module and if no errors are encountered to prevent this. When errors are
encountered, the transaction code VFX3 must be used to check/resolve the error and release the blocked
documents to accounting. It displays all billings documents that could not be processed and released to
accounting. They have been generated but failed and no outputs can be created and printed out.
Possible types of errors include following examples:

1) Accounting blocks
2) Error in accounting interface
3) Pricing error
4) Foreign Trade data error
5) Authorization error
It is especially important to complete the review in VFX3 before each period end and ensure exceptions are
investigated and resolved. This activity must be a daily task of the Customer Service team. Run this report
after the billing run/creation.
1. Enter transaction code VFX3 in the command field and click (Enter).
Date: 18-May-2021
Page 21 of 48
3. Remove the user ID from Created By field
4. In the Creation Data section type the current date in the “to” field of the Created On
5. Tick all types of errors in the Incomplete due to section
6. If you want to narrow down the selection criteria to 3 rd party invoices only, type the ZF2 in the Billing
Type field
8. Extract the VFX3 report to Excel if you want to keep the daily log to see how many days a particular
document has been held (recommended from KPI point of view).
Date: 18-May-2021
Page 22 of 48
9. Select all items.
10. Right click on the grey button and choose Spreadsheet, then select a formal of your file.
11. Save the file in the desired location.
2.2.1 Identification of VFX3 errors and resolution
Every line in the VFX3 report must be investigated and the reason of error must be identified by the
Customer Service Analyst and resolved appropriately.
1. Select all documents and press Release to Accounting button
2. Go to the column Processing Status and check Documents that could not be processed (they will
display ). These documents will require further investigation.
In order to check what type of error prevented the billing document from being transferred to accounting go
to the column in the report called “Incomplete due to”. You will see multiple types of errors there.
To get more details about each error review the error log, investigate the nature of the issue and follow up
with the right team to resolve it immediately (or resolve yourself if you have the right access to do so).
3. Click on the error log (Notes) button
Date: 18-May-2021
Page 23 of 48
4. Click on to see the technical details of the error.
5. Review the error message and address to the relevant team if the error cannot be resolved by
yourself.
Pricing error
Once the pricing error has been identified Customer Service Analyst needs to investigate further to
understand the specific cause of the issue by looking at individual documents.
Errors in pricing could be due to the following:

- The pricing has changed between requested delivery date and billing date.
At the time of billing prices are taken based on requested delivery date, if the price is missing then it might
end up as the pricing error in VFX3.
- The tax condition records which determine tax rates for every SKU. This is not controlled by
Customer Master data only, but each payer should be set up with the correct tax code (e.g. MWST
for tax) which impacts the tax determination.
- Intercompany/Buy-Sell transfer pricing process. The price in PIR is not created at the same time as
the price in SD. The responsibility of setting up transfer prices belongs to BSG team and they should
monitor it on regular basis. To successfully invoice, the transfer price must be fully completed while
creating STO. System checks prices from PIR so if anything is not set up, it will end up as the pricing
error. The output Z2HU to HQ will never get sent if the error in VFX3 is not fixed first.
Date: 18-May-2021
Page 24 of 48
1. Go to VF03 transaction and type the billing document number
2. You will see the error message Pricing error in item XX
Missing price in VFX3 report can be caused by the following issues:

 Price was missing at the time of the billing document generation but it has already been loaded to
the system
 Pricing deletion flag has been added to the item
 Pricing obsolete
 Mismatch between the price validity date (from – to) and the sales order pricing date
Date: 18-May-2021
Page 25 of 48
3. Select the line that shows the error and click on the Item Pricing Condition button
4. Select Analysis button which will redirect you to the pricing conditions screen where you can identify
if the price setup is missing.
The Customer Service team cannot solve pricing queries hence you will need to contact the team who is in
charge of the Pricing Master.
Date: 18-May-2021
Page 26 of 48
5. Go to details of the pricing condition that has caused the billing error
6. Review which price is missing and contact relevant team
FI/CO Interface errors (accounting interface error)
FI/CO error occurs when the document “Billing date” and “Created On” date is not within the same fiscal
period. "Created on" date is a date when we receive the error in VFX3 for the first time. "Billing date" is when
the document has been billed. When we bill older documents from the past months (when the period is
already closed), we would need to create based on the current date. Billing batches are set to look at
document dates from a specific date to current. These documents being a bit older as they have been stuck
in the system for quite a while, are not going to be picked up by the batches.
FI/CO error can also be triggered by documents with more than 999 items, due to the invalid tax code or
when the customer is set as obsolete.
Resolution of such error fully sits with Customer Service team without any dependencies.
1. Go to VFX3 transaction
2. Check documents with the error FI/CO interface

4. You will see the list of error(s) encountered in the given document.
Date: 18-May-2021
Page 27 of 48
5. Click on to see the technical details of the error
Date: 18-May-2021
Page 28 of 48
To resolve the error you will have to change the Billing date.
6. Go to the transaction VF02. Alternatively you can select the line of the billing document which did not
post to accounting and click on the pencil (which will take you directly to VF02)
7. Click on Display Doc. Header details
8. Type the current date in Billing Date field
Date: 18-May-2021
Page 29 of 48
9. Save the document
10. Go back to VFX3 and click on Release to accounting and check in the document flow if the
accounting document has been generated.
Invalid Tax code

If the error has been caused by the invalid tax code you will see a similar message as below.
As this error stems out from the configuration issue an Assist ticket has to be raised to fix it.
If the error has been caused by the fact the document contains more than 999 items the proposed solution is
to cancel the existing billing document and split items from the outbound delivery into two groups and rebill it
again.
Date: 18-May-2021
Page 30 of 48
Account determination error (accounting block)
This type of error can be caused by several reasons:

 No G/L assignment has been found (configuration problem)
 Customer account assignment group missing in the Customer Master data (data issue)
 Wrong account assignment group for the material – by default this is set to 01 but changing schedule
line item category in sales order processing (transaction VA01) changes the account assignment
group
 Revenue account determination settings (configuration problem)
 Account Keys and G/L accounts for taxes
 Material Master data (sales org 2 tab - Account Assignment Group is not maintained)
 Missing tax code or discount conditions (this is most probably problem with the set up in Customer
and Material Master data)
 COPA value mapping missing (configuration problem)
 Issues with the product substitution (configuration problem)
 Marketing samples – when users try to select TANN item category for marketing samples (system
will always default it to ZMKT item category).
2. Check documents with the error Acct.determin.error

Date: 18-May-2021
Page 31 of 48
5. Copy the billing document number and go to VF02 transaction
6. Press Enter
7. Go to Header and then select Header
Date: 18-May-2021
Page 32 of 48
8. Check the field Cust.Acct.Assg.Group. In this example the value should be 01 Domestic
revenues. In some other cases, depending on the ship to, the account assignment group could be
“06 marketing samples rev” for example. If you have a doubt, ask your customer master data team.
So that the error does not repeat, master data team will need to correct the master data record.
Date: 18-May-2021
Page 33 of 48
If the error has been caused by a different reason you will have to either raise an Assist ticket or
communicate with data steward to fix the data source.
Foreign trade data error
This type of error can be caused by missing material commodity code. There are multiple check points to
ensure the foreign trade data is correct however it all depends on the configuration made for each market.
2. Check documents with the error For.Trade data


6. Press Enter
7. Select the line item with the error
Date: 18-May-2021
Page 34 of 48
8. Go to Item and then select Foreign Trade Item
9. Check if the commodity code number is populated in the field Comm./imp. Code no.
A. If the commodity code is not populated in the billing document follow below steps:
10. Press Set until it changes status to Deselect
Date: 18-May-2021
Page 35 of 48
11. Copy the material number from the field Material
12. Go to the transaction MM03 and paste the material number
13. Select Foreign Trade: Import Data and hit Enter
Note: You can find the plant number in the Item detail tab of your billing document.
Date: 18-May-2021
Page 36 of 48
14. Insert plant number in the Plant field and hit Enter
15. Copy the commodity code from the Comm./imp.code no. field
Date: 18-May-2021
Page 37 of 48
16. Paste the commodity code number in your billing document (transaction VF02)
Date: 18-May-2021
Page 38 of 48
Note: Before populating the commodity code ensure that City of Origin and Dispatch country are entered as
well as the Export procedure (must be 1 - Permanent Export) and Business transaction type (must be 10 –
Final purchase/sale).
Date: 18-May-2021
Page 39 of 48
B. If the commodity code is populated in the billing document just save the document. Go and check the
document flow to ensure the accounting document has been generated.
One of possible foreign trade data errors might be also missing Business Transaction type data. In this case
please follow below steps:

20. Press Enter
21. Select the line item with the error
22. Go to Item and then select Foreign Trade Item
23. Go to the tab For Trade/Customs and then select tab Origin/Destination/Business
Date: 18-May-2021
Page 40 of 48
24. Populate the field Bus Transact Type with the correct value. Normally it should be 11 - Final
Purchase / Sale.
Error in authorization
Please contact your support team to review the role assigned to the user as CS admin and manager have
access to billing a document.
Date: 18-May-2021
Page 41 of 48
2.4 V.21 log of collective run – alternative to running VF04 and VFX3
We have explained above how to use VF04 to check documents overdue for billing and billing errors.
If a document is overdue for billing (i.e it should have been billed but it has not), it will be due to an error
preventing the billing from being done.
The primary purpose of VF04 is to bill documents manually.

By doing so, VF04 will indicate if there are any errors preventing billing, but this is just the outcome/result of
running the billing due list.
There is an alternative to using VF04 to identify any billing errors and this is to use transaction V.21 log of
collective run.
The purpose of that transaction is to show the outcome of a batch job, either run manually or automatically.
This means that V.21 can show:
- The documents created following an automatic or manual billing using VF04
- The potential billing errors but also accounting errors
By running V.21 you will get the same information as by running VF04 and VFX3.
The markets can choose which option they prefer. Running V.21 may be more efficient especially now that
the default billing method is to use expected POD or actual POD as VF04 does not enable to check
documents overdue for billing easily as the billing date always reflects the PGI date.
Go to transaction V.21
Ensure that the type of collective run is “F” invoices from VF04
In the “started by” field input the name of the batch job you want to get the log for. If the batch was run
manually by a user, input the user’s ID
The batch will have the format “WF-BTCH-xxxx” where “xxxx” stands for the sales organisation
Input the date of the run that you want to get the log for, usually yesterday to today
Leave the boxes under “list selection” as shown below
Type of collective run must be as “F” which is for the billing
Once the transaction has run, you will see the number of documents created displayed and the number of
errors
Date: 18-May-2021
Page 42 of 48
To see the detail of the documents created, select a line by single clicking on it and then click on the button “
To see the list of errors, select a line by single clicking on it and then click on the notes button.
You will get the detailed list of all the errors that you will have to investigate and solve as shown previously:
You can use the button to group the same errors together
Date: 18-May-2021
Page 43 of 48
You can then use the button to go back to seeing each error individually
Clicking on the folder icon provides more information on the error
The log will also indicate accounting errors. This means that the billing document was created (like in the
example below where you can see the billing document number) but the accounting document was not:
Important:
If an error is preventing a billing or accounting document from being created it will recur/repeat in each billing
run.
You cannot differentiate between the sales organisation billing run and intercompany billing runs which are
both shown in V.21.
In the example below, the error is recurring every time the sales organisation billing runs.
The reason why it does not appear in the last run is because this is the inter company billing run.
You could believe that there is no recurring billing error, but in fact, every time the sales organisation billing
has run, the error was displayed.
2.5 VOEX Foreign Trade: Operative Cockpit: Export Billing Documents

If transaction VFX3 has highlighted errors due to foreign trade data, run this transaction to look for where
there is foreign trade data missing in billing documents.
V.21 will also indicate these errors
IMPORTANT: Foreign trade data missing does not necessarily prevent the accounting document from
creating which means these issues will not be recurrent at each billing run in V.21
As it does not necessarily prevent the accounting document from being created you would not see any
missing document in VFX3. You would not see any documents due for billing in VF04 either.
This is why you need to run VOEX too.
1. Go to VOEX transaction
As you are checking foreign trade data, this is checking the information which is needed and determined for
export orders, such as ZICO intercompany sales orders used to resupply other Reckitt sales organisations
which are still on JDE.
Therefore, you have to input the whole rage of countries in the “country” field to make sure you are not
missing any export country.
Date: 18-May-2021
Page 44 of 48
2. Type the sales organization
3. Type the required Billing Date
In the “incompletion” tab untick the “complete” check box so that you see only the incompleteness:
In the following screens, the “complete” box was ticked, hence why some lines have green status
You will see the report which looks like below.

- The green status means the document has been successfully processed – no action required here.
- The red button symbolizes some foreign trade data is missing in the billing document and must be
resolved by the Customer Service Analyst.
Date: 18-May-2021
Page 45 of 48
5. Select the billing document with the red status and click on Log of Incomplete Items
6. In the Incomplete fields section you will find details about what data is missing and whether in the
document header or line item. In the example below it concerns both: the header ad the item.
7. Click on to expand FT header and FT item
8. In the FT header select the correct value in the field where data was missing, in this example: Mode
Of Trnsprt-Border and Domest Mode of Transp.
9. Update the information with the correct data for your market. The below print screen is just an
example
Date: 18-May-2021
Page 46 of 48
10. The status in the FT header will change to green
11. In the FT item select the correct value in the field where data was missing, in this example: Country
of Origin in the Origin / Destination / Business tab
Update the information with the correct data for your market. The below print screen is just an
example.
12. The status in the FT item will change to green

14. In case the accounting document had NOT been cerated due to the error, check in the document
flow to make sure the accounting document has been generated.
NOTE:
The foreign trade data comes from material master data and configuration.
Therefore CS cannot correct the root cause of the problem, they can only edit and complete the specific
billing document.
Date: 18-May-2021
Page 47 of 48
This means that CS will need to inform the master data team to get the information completed, and if
required also raise a ticket to Assist.
3 Reports
N/A
4 Approval
Signatures below only when not included in digital signatures
Updates
Approver Name Job Title or Roles Approval Date
Mike Picton Senior Business Analyst SD 5th August 2019
How to run VF04 for
Lisa Bentley Solution architect SD March 3rd 2021 POD markets ;
transaction V.21
5 Updates
Updates Date
Updates table created May 18th 2021
Details added to V.21 run May 18th 2021
Date: 18-May-2021
Page 48 of 48

USG Billing Errors Management VF04 VFX3 VOEX SAPERP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

USG Billing Errors Management VF04 VFX3 VOEX SAPERP

Uploaded by

Copyright:

Available Formats

Billing Errors Management

VF04 / VFX3 / VOEX / V.21

1.2 Process description and scope

2.1 VF04 Maintain Billing due List Report

Possible types of errors include the following examples:

2. In the Billing Data section leave a Billing Date from blank.

8. Select all items.

Analysing the results:

Documents with POD status “blank”,

2.2 Identification of VF04 errors and resolution

11. To bill all documents select them all and click on or .

12. To bill one document select it and click on

14. Click on the error log

Blocked for Billing

2. Click on the Document flow

4. Check if the Temporary Block in Billing block field is set up.

5. Click on Doc.header details .

9. Save the sales order .

Proof of Delivery (POD)

1. Go to Edit and select Log.

3. Go to Edit and select Incompletion log.

5. Highlight the item line and click on Item conditions .

User Status FIAR block

The error message will show below details.

Possible types of errors include following examples:

2.2.1 Identification of VFX3 errors and resolution

1. Select all documents and press Release to Accounting button

display ). These documents will require further investigation.

3. Click on the error log (Notes) button

Errors in pricing could be due to the following:

Missing price in VFX3 report can be caused by the following issues:

FI/CO Interface errors (accounting interface error)

2. Check documents with the error FI/CO interface

3. Click on the error log

7. Click on Display Doc. Header details

8. Type the current date in Billing Date field

Invalid Tax code

This type of error can be caused by several reasons:

2. Check documents with the error Acct.determin.error

3. Click on the error log

7. Go to Header and then select Header

Foreign trade data error

2. Check documents with the error For.Trade data

3. Click on the error log

5. Copy the billing document number and go to VF02 transaction

7. Select the line item with the error

10. Press Set until it changes status to Deselect

19. Copy the billing document number and go to VF02 transaction

21. Select the line item with the error

22. Go to Item and then select Foreign Trade Item

25. Save the document

The primary purpose of VF04 is to bill documents manually.

Type of collective run must be as “F” which is for the billing

Clicking on the folder icon provides more information on the error

2.5 VOEX Foreign Trade: Operative Cockpit: Export Billing Documents

This is why you need to run VOEX too.

4. Click Execute (F8) to run the report

You will see the report which looks like below.

7. Click on to expand FT header and FT item

12. The status in the FT item will change to green

13. Save the document

You might also like