Error in VF04

Hi,
When i run VF04 it shows deliveries due to be billed. However when you look into the delivery, it has been deleted. My question is: Why are they showing on the billing due list if they have been deleted and how can you resolve this to come off the report?
Regards,
Rahul

Dear Mr Rahul Dev,
Deliveries due to billing are available as part of the table VKDFS.
Could you kindly verify the existence of these entries.
If so, they can be cleared.
Regards,
K Gopidas.

Similar Messages

TSV_TNEW_PAGE_ALLOC_FAILED Error in VF04 tcode

Hi Guru's
When I am executing T-code VF04 (SDBILLDL) with Input value,I am getting dump of " TSV_TNEW_PAGE_ALLOC_FAILED alon with the short Text " No more storage space available for extending an internal table."
Is it has any SAP notes for solving this problem.???
Regards
P.Senthil Kumar

Hi Volker Binder,
We unable to inform basis people to extend memory space in our system without giving any proper notes..
i want to give detailed solution for this then only basis people extend the memory space..
is it has any sap notes for solving this issue..
Regards
P.Senthil Kumar

Showing by error in VF04

Hi gurus,
Two intercompany deliveries have been invoiced but by some issue they have been showing up in the VF04. What would have been gone wrong? How to clear it from there since it is already been billed.
Plz help me in fixing it.
Thanks in advance.

hii Singh,
Pls chk ur intercompany billing type is correctly mentioned in ur order type or not.
regards
Monteee

VF04 - Error Codes

Good Afternoon all,
hopefully i have posted this question in the right section..
i am trying to comply a list of all the error codes with in the VF04 Function, and was wondering if there is an easier way of getting this information, as currenly i am having to run the report, then go onto each order, to find the code, and the reason, and then log it down.
if there is away of finding this with in SAP, or does anyone here have a list they could show me.
your help will be greatfully recieved
regards
Jonathan

Hi Jonathan Lebbon,
Will plz tell me in what error is getting in VF04?
and give an example...as it is just a due list of Invoices, there wont be any Errors in VF04.
Thanks,
Neelima.

Error messages in invoice pool (VF04)

Hi!
When i use transaction VF04 to invoice if there are any standard errors, the transaction ends all invoices and shows a report with a log of the errors; but the important is, that it finishes all the invoices.
The problem is if i put some message error by a user exit. If I use VF04 and one of this invoice have a error message (own, no standard) the program stops. I mean, if I have 4 invoices and the error is in the second one, the next two invoices are not done.
So i want to put this message errors into the reports like the standard messages. Maybe is some properties of the message, but i'm not sure.
Thank's in advance!
Cheers,
Xavi.

Hi Xavier,
I see this post is pretty old, I have a similar problem with yours - how could I find out how to issue some error messages from one of the VF04's exits the "standard way" - I'm tanking about the EXIT_SAPLV60B_001 .
Thank you in advance,
MM

VF04 - Error System error in: table: report: LFMRIF02 routine: SET_NUMBER

Hi guys,
I'm currently getting an error when I run VF04 with more than 999 sales orders. The error which I'm getting is:-
"Error System error in: table: report: LFMRIF02 routine: SET_NUMBER"
Upon further debugging, I found out that Buzei is the line item number and in the subroutine SET_ITEMS (Include LFMRIF28) l_buzei is incremented by 1 each time we encounter an empty/000 line item number. Unfortunately when l_buzei is at 999, an addition of 1 takes it back to value 000. It is this 000 value that triggers the error message we had seen in subroutine SET_NUMBERS (Include LFMRIF29).
Has anyone encountered this error before? Some points as to where I can start would be helpful.
Thanks.

Hello..
Your suggested OSS note was created 2006, nevertheless it was still helpful for me to start my search from there. Also for that note, it will effect the Funds Management reporting line items, it will simply don't appear.
Better alternative would be OSS 964228, this basically skips the '999' items and proceed. No affects on the funds management reporting either.

Filter criteria on added field in VF04 gives error and does not filter

Hi!
I have added a filed WBS to the output of VF04 using a exit. What I did was added the wbs filed to the table VKDFIF table and then used the exit ZXV6PU08 to get the values in the VF04 output. The display output for VF04 does bring in the values for the WBS field that I added . NOw when I want to do a filter on the field it pops out an error message :WBS element 00000 does not exist. But when I fill in the selection criteria in the filetr screen in ranges i.e lower value and upper value it displays me the filtered value, its only when I enter values in the lower range only it pops out a message saying the value does not exist and it does not do the filter.
Can anyone please tell why this is happening and how it can be fixed?
Thanks

Hi Odysseas!
I ahve a program which finds the user exit for any transaction and I used that for VF04 and choose the right exit applicable to your requirement. This will lead us to the user-exit , I chose V60P0001 form the list for my requirement and when you drill down it will take you to the desired program include zxv6pu08.
I hope this would be helpful for you . PLease do let me know if you need any more information on this.
Thanks

VF04 - error message types

Good Afternoon all,
hopefully i have posted this question in the right section..
i am trying to comply a list of all the error codes with in the VF04 Function, and was wondering if there is an easier way of getting this information, as currenly i am having to run the report, then go onto each order, to find the code, and the reason, and then log it down.
if there is away of finding this with in SAP, or does anyone here have a list they could show me.
your help will be greatfully recieved
regards
Jonathan

Let me start with saying that this requirement is, well, stupid. Even if it was possible to find all possible error messages, 99% of the errors most likely would not even apply to your business.
Technically, if you've gotten to billing (VF04), there should be no errors at all at that point. I would rather concentrate on refining the process, configuration, etc. to prevent any error, than trying to figure out all "what ifs".
If you still would like to oursue this meaningless, in my opinion, task, you might want to look at the message class VF in SE91 transaction. Also, you can try searching for MESSAGE command in the main billing program and all sub-programs. Good luck with that.

Error while creating billing document using VF04 transaction

Hi All,
User is trying to create billing document using VF04 with ference to delivery number. When pressing save in invoice creation system SAP gives invoice document number (No accouting document generated). but no documents are actually created. When user trying for second time log is showing this sales order is currently processed by the user(user is same who is trying to create invoice)
Please let us know what is causing this issue since this issue is happening in production and we can not debug this.
We checked for number range also but its not.
Waiting for your inputs.
Regards,
Jyothi CH.

When pressing save in invoice creation system
SAP gives invoice document number (No accouting document generated).
but no documents are actually created
Check there is any clash with internal number range of billing type vs other billing types ?
Try to create billing document using VF01,see any messages were poping while saving ?
Check for abap dump in ST22 ?
Edited by: Jeyakanthan A on Feb 9, 2011 9:52 PM

How can we remove items from the VF04 list?

We have a long list of items in VF04 that, for various reasons (some process related, some due to errors), are not to be billed. We have looked at applying filters to the list but there is nothing really suitable to hide these individual documents e.g. we could filter out some dates where none of the items on that date are to be billed but other dates have a mix of items we want to bill and others we don't.
I have done a search of this forum but didn't find a previous topic with a quick and simple method to remove items from the list .
Is there a method, other than billing them or sorting each issue individually, to permanently remove individual documents from the VF04 list?
Thanks in advance for any help.
David

Hi,
David,
Download a list of Pending delivers doc form VF04.
Paste the list in T.Code : VL09 (Delivery reversal) and reverse the delivery.
Then go to T.Code: VL06G Select the list of deliveries that has been reversed, select/delete all un- wanted deliveries.
This way you can remove all unwanted pending deliveries forn Billing due list (VF04).
Thanks & Regards,
R.Janakiraman

Error 70 - Código do status 225: Rejeição: Falha no Schema XML da Nfe.

Bom dia grupo!
Nós estamos atualmente recebendo a seguinte mensagem de erro da SEFAZ relacionado aos batches que nós enviamos: Error status 70 "Error from the authorities" and Código do status (Status Code) 225: Rejeição: Falha no Schema XML da Nfe.
Nossa configuração é 46C com muitos OSS notes aplicados (veja abaixo)
Nós estamos realmente parados neste momento e não temos nem ideia de onde começar.
Atenciosamente,
Marc de Ruijter
OSS notes for NF-e phase 2
989115      Nota Fiscal Electronica (NF-e) - Overview Note
852302      Implementation Overview ISS 2004 - Legal Change MP135/LC116
759965      New Condition Formulas for MP-135 and ISS 2004
747607      Basic Customizing for MP135 and ISS legal change Brazil
980214      DDIC changes: PIS / Cofins Tax Law and Tax Situation
981123      PIS / Cofins Tax Law and Tax Situation
981687      NFe: For Services in Muncipio Sao Paulo
934846      Syntax error: TYPE-POOL 'SXRT' is unknown
979881      Message S 000 in NF writer when mandatory fields not filled
980213      Nota Fiscal Electronica (NF-e) of SEFAZ - Phase 2
1037070      NF-e of SEFAZ - Phase 2, Enhancement 01
1014600      No output found for the Nota Fiscal
1052575      NF-e of SEFAZ - Phase 2 / DDIC changes after shipment
1043688      NF-e of SEFAZ - Phase 2, Enhancement 02
1062468      NF-e: Multiple volume structure for XML file
1062251      NF-e: Extension of BADI Interface FILL_HAEDER
1070261      NF-e of SEFAZ - Phase 2, Enhancement 03
1094041      NF-e of SEFAZ - Phase 2, Enhancement 04
1000130      Public System for Digital Bookkeeping (SPED) - Overview Note
1008306      SD: Manual changes of CFOP for services when ISS tax applies
998194      Missing ISS Tax Situation in the Nota Fiscal
1047606      SD/Brazil: Using of error log during Nota Fiscal creation
120449      SD-Brazil Exchange variance error in Nota Fiscal
92383      LSA:BR:SD: Tax laws in return nota fiscal
689157      Nota Fiscal Split and number of Packages
987882      ISS Tax Law (field J_1BTAXLW3) not copied from sales order
989965      CFOP redermination in the delivery document not working
909835      Message 8B 679 raised during the delivery process
337554      SD: No. of packages in Nota Fiscal
533046      Repair order inconsistent to object list
920330      Error when changing the tax codes in a sales order
998195      PIS/COFINS/ISS Tax Law and Tax Situation in SD
104606      EDI/IDoc: Mapping IDoc types to ANSI X12
1094041      NF-e of SEFAZ - Phase 2, Enhancement 04
1105588      J_1BLFZF: Runtime error OBJECTS_OBJREF_NOT_ASSIGNED
     OSS notes for XML ver 1.1 and NF-e phase 3
1065334      NF-e: Extension of BADI Interface FILL_ITEM with tax table
1068615      NF-e: Extension of BADI Interface with SD document flow
1079826      NF-e: BAdI Interface Enhancement for NF Messages
1069919      NF-e: Partner in Block E should always be main partner
1090279      NF-e monitor: automatic refresh upon user actions
1093252      NF-e: ICMS tax situation in XML File and DANFE
1113127      NFe: New XML Layout - Version 1.10
1114348      NF-e - xNFe integration - backend
1122294      Send/resend NF-e: fill VBFA for BAdI item method
1124075      NF-e: Serie not taken from Contingency NF-Type
1144194      NF-e: Cancellation/Skipping Reason
     Bug Fix notes for NF-e BAPI.
1049946      NF-e: Adaption of Nota Fiscal Bapis
1147934      NFe: Random number should not be generated for incoming NFes
1150733      NFe: Randon number and check digit not cleared
1154995      NF-e: NF BAPI - enhancement for NF-e processing
1158622      NF-e: NF BAPI - no input of random number possible
     Bug Fix notes for Contingency process
1158612      NF-e: Wrong partner in Block-E for Entrada
1240212      NF-e: One time Vendor data not transferred to XML file
1255450      NF-e: Jurisdiction code for one time vendor / customer
1257030      NF-e: Country Name for one time vendor / customer
1069018      Cancellation of incoming NFe shows error J1B_NFE 003
1070077      NF-e: Protocol number and document status for Denied NF-e
1145148      NFe: Cancellation for Contingency NFes
1152263      NF-e monitor: wrong action status '7' for C-NF-e
1146914      NFe: Synchronous call to messaging system from backend
1149356      NFe: Dump when NFe is cancelled with MIGO
1152081      NFe: Dump when NFe is cancelled with VL09
1153533      NFe: Dump when NFe in contingency is cancelled with VL09
1156116      NF-e: Contingency by stock transfers
1160107      NF-e: Cancellation of contingency NF-e with DOCSTA = 1 or 2
1161347      NF-e: Cancellation of Contingency NF-e - correction
1238648      NF-e monitor: req. action '3' (send) wrong for swtch. NF-e
1165953      NF-e: Numbering Gaps
1244326      NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP
1245425      NF-e monitor: required process step - contingency
1252567      NF-e: Resend of NF-e - rejected or with validation error
1266344      NF-e: Action Indicator for NF-e with validation error
1254565      NF-e: Synchronization of RFC call between ERP and xNFe
1053626      MIRO: wrong document reference in nota fiscal
1073259      NF-e: Transfers - Outgoing NF-e No. not taken by Incoming
1153874      NF-e: GR for future delivery takes wrong NF-e number
1174946      NF-e: Serie not considered for duplicate NF-e number in MIRO
     Miscellaneous bug fix notes
1175538      NF-e: Reference between NF and NF-e
1244881      NF-e: Mixed scenario in MIRO shows error 8B219
1257422      MIRO: Error 8B 219 by posting of reference invoices
1150843      NFe: Text for cancel reason not transferred to XML file
     Bug Fix Notes Group 2
1059699      NF-e: Reference between NF and NF-e
1139062      NF-e incoming: Posted via J1B1N -> Wrong Document Status
1144199      NF-e: SD Billing and Contingency
1145089      NF-e: Cancellation despite rejected cancel request
1149787      NF-e: Wrong status-code text in NF-e history
1151112      NF-e: cancellation-reason text gets lost (pre req of 1150172)
1150172      NF-e monitor: selection leads to dump
1068379      Creation of Billing document issues an error 8B 145 (pre req of 1145089)
1152842      NF-e: cancellation reason does not work
1154700      NF-e: Random number & check digit not stored in active table
1073145      PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
1082527      Missing PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
997868      VL02N: CFOP, tax laws not copied from delivery (error 8B148) u2013 (pre req of 1155231)
1155231      PIS/COFINS tax law in NF/NF-e by split valuated material
1155424      NF-e monitor: Menu -> "Check MS Connection" does not work
1159177      NF-e: FUNC J_1B_NFE_SET_STATUS_IN_BACKEND set as Rem.Enabl
1161951      NF-e monitor: "Resend" functionality.
1162232      NF-e: switch to contingency not possible after MSS Update
1162512      NF-e: cancellation reason not initial at first-time call.
1162629      NF-e: creation date gets deleted from NF-e data-base table
1164283      NF-e: SCS '5' - upon authr.to cancel system does not cancel
1165155      NF-e Monitor: BACK (F3) leads to cancellation
1165360      NF-e Monitor: new selection parameter - creation user
1168394      NF-e: Reference document not taken from Nota Fiscal header
1168798      NF-e: User decision for used NF-Type for Material Movements
1171383      NF Writer: Copy NF-e that was switched to contingency.
799445      Nota Fiscal creation: Consideration of local dates (pre req of 1171383)
1104003      NF-Writer: Serie not taken from Reference NF (pre req of 1171383)
1156037      NF-e: NF-Writer allow reference with different NF-types (pre req of 1171383)
1175759      NF-e: central contingency per business place - correction
1239598      NF-e: Random number and check digits are lost in NF writer.
1163888      NF-e: Random Number includes spaces (pre req of 1239598)
1245425      NF-e monitor: required process step u2013 contingency. u2013 applied in bug fix notes no need to apply.
1246700      NF-e: Wrong reference for NF entradas.
1257688      NF-e: Update termination with error J1B_NFE 021
1258021      NF-e: Dump by creation of NF header text for XML file
1258974      NF-e: Monitor report aborts with DBIF_RSQL_INVALID_RSQL
1265172      NF-e - Decouple RFC from DB Update
1285851      NF-e: Cancellation of none authorized documents
1288925      NF-e: References between NF-e and non NF-e
1272677      NF-e: Cancellation for Material Document with serial number (pre req for 1288925)
1247602      NF-e: Cancellation of material documents with serial numbers
1163104      NF-e: Cancel Material documents with initial cancel reason
1293944      NF-e: Cancellation of material documents with batch classes.
1267128      NF-e: Cancellation goods movement with MVT 844 not possible (pre req for 1293944)
1300000      NF-e: Decouple - Contingency
1314856      NF-e: Decouple - Contingency in J1BNFE and VF01 & VF04
1321837      F-e: Cancel of material documents not possible
1092028      NF-e: Protocol number in NF-header overwritten (pre req for 1265172)
1114283      NF-e: cancellation - document status cleared in J_1BNFDOC (pre req for 1265172)
1234053      Local time / local date in NF header and NF-e XML (pre req for 1265172)
1288994      NF-e: Decupling note 1265172 causes error for incoming NF-e (pre req for 1300000)
1297042      NF-e: NF-e number missed in access key after decoupling (pre req for 1300000)
1087535      RFFOBR_A,U:Doc.no should be filled with 9 digits in DME file Applied OSS note 1087535 to the object Z_RFFORIY1 which was copied from RFFORIY1
1097455      NFE: Bank files should accommodate Doc. Numbers with 9 digits
304961      Wrong boleto check digit with carteira data (pre req of 1097455) - Not relevant
336117      Include due date factor in Boleto barcode for A/R (pre req of 1097455) - Not relevant
705726       ITAU: Boleto has negative interest value (pre req of 1097455) - Not relevant
846297      Func Mod - BOLETO_DATA not printing correct nosso numero (pre req of 1097455) - Not relevant
852782       BOLETO_DATA - Corrections of note 846297 for Bredesco only (pre req of 1097455) - Not relevant
1227478      Dump in payment run (F110) when XBLNR is empty
1138278      NFe: Field PREDBC not filled in XML interface structure (pre req of 1149585)
1149585       NFe: CST field required in XML file for taxes not in NFe
1053855      VL02N raises error 8B 053 "Branch not foundu201D
1165696      RFEBBU00: Error in batch input due to changes in Nota Fiscal
1180402      NF-e: BADI methods FILL_HEADER and FILL_ITEM
1180672      NF-e: Gap numbering check doesnu2019t consider the series
1225338      RFEBBU00: Additional changes to the note 1165696
1241922      NF-e: Report J_1BNFECHECKNUMBERRANGES xNFe adaption
1244326      NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP (Applied using other Kintana)
1270813      NF-e: Year not included in the XML file
1247264      NF-e: Error in RFC to /XNFE/NFE_CREATE after note 1241922 (pre req for 1274200)
1274200      NF-e: Numbering gaps report sends SERIE with spaces
1276185      NF-e: Numbering gaps report sends SERIE with spaces
1294917      NF-e: Gap numbering check - several corrections
1324538      Missing address for OT Customer in J_1B_NFE_CREATE_TXT_FILE
1331432      NF-e: Numbering gaps report detects gaps for initial series
1332167      NF-e: Rep. J_1BNFECHECKNUMBERRANGES aborts with error DC 006
1092341      RFFOBR_A,RFFOBR_D: Performance problem while rebate calcula
1237089      RFEBBU10:While uploading ITAU Bank returnfile- Error(F5 170)
1051314      Check Digit missing from Boleto number (pre req for 1306966)
1306966      J_1BBR30:XREF3 is not updated correctly with Boletofrom bank
1005924      RFFOBR_A-The DME file does not include Rebate for ITAU (pre req for 1287633)
1287633      RFFOBR_A: Discount amount not calculated correctly
1234054      NF-e: function J_1B_NFE_MS_REQUESTS_DATA is not RFC enabled
1297534      NFe cancellation problems in GRC
1243964      NF-e: Adaption of xNFe interface of function NFE/NFE_SKIP
1165746      NF-e: Cancel - Error log not updated
1327465      The program /xnfe/update_erp_status is not updating R/3
1326691      BAdI for controlling the RFC call of external systems
1333136      Prevent simultaneous click on buttons in NF-e monitor
1333742      NF-e got the status 218
1354192      Validation rules: correction for fields TPLACA and T_UF1
1373175      Lock object for /XNFE/NFE_CREATE to prevent double transm
1376500      BAPIRET2 to provide the detailed information to ERP
1267455      Not possible to create different DOCREF per item using BAPI (pre req for 1373321)
1373321      BAPI_J_1B_NF_CREATEFROMDATA: DOCREF from Header go to item
1328583      NF-Writer posting of NF/NFe when mandatory fields not filled
1338166      NF-e: Random number and check digit lost after note 1328583
1259918      NF-e: RFC calls for request for cancellation or skip
1152140      NF-e: backend allows inconsistent new SCS (pre-req for 1298283)
1162852      NF-e: Inbound errors missed in error log of Monitor Report (pre-req for 1298283)
1163056      NF-e: Problems with printing via BADI method CALL_RSNAST00 (pre-req for 1298283)
1276438      NF-e: Parallel Phase not identified in messaging system (pre-req for 1298283)
1296515      NF-e: J1BNFE reset rejected NF-e after skipping request (pre-req for 1298283)
1297823      NF-e: Cancelled NF-e shows wrong action indicator (pre-req for 1298283)
1298283      NF-e: Skip for NF-e with validation error
1362969      NF-e: check cancellation for billing documents
1368159      NF-e: cancellation of invoices via original application only
1370933      NF-e: Accept Rejection to Cancel - wrong status in monitor
1376324      NF-e: Skip for NF-e with validation error
1140579      NFe: Field length conflicts from backend interface to XML
1357713      NF-e: Cancel of incoming NF-es does not update active table.
1173018      NF-e: Field control for Random Number and Check Digit (pre-req for 1366320)
1321517      NF-e: MIRO Credit Memos for NF-e shows error 8B 020 (pre-req for 1366320)
1366320      NF-e MIRO:Save is allowed without mandatory fields filled for NFe
1375066      NF-e: J_1BNFECHECKNUMBERRANGES ends too early, wrong subrc
1375894      NF-e: J1BNFE authority check for company code
1377879      NF-e: Report J_BNFECALLRFC aborts with message A098
1379062      NF-e: posting GR after cancellation leads to wrong NF-e
1357777      Cancel billing document without Nota Fiscal cancellation
1380861      NF-e Resend(proc.stat.07) with Signature error impossible
1362025      Error while sending Bacen Code EX with 0 on begining
1249819      NF-e: Field MODFRETE filled incorrectly

Bom dia Marc de Ruijter,
Não dá para ler sua thread, mas imagino que seu validador esteja desligado.
No GRC vá em SPRO --> SAP GRC Nota Fiscal Electronica --> Configure System Response for Each Tax Number (CNPJ)
Para ligar/desligar o Validador basta clicar no check box na coluna Validation.
Observação: Para correto funcionamento do GRC deve-se sempre utilizar o validador ligado.
Após isto refaça seu teste, é provável que você receba um erro de validação para a NF-e. Veja em GRC Web monitor -> NFe Detailed View -> Validation History.
Atenciosamente,
Fernando Da Ró

Error while creating inter-company invoice for stock transport

Hi ,
I am facing following errors while creating inter-company invoice for STO order.
We have scenario where standard PO is created in company code A & then replenishment delivery is created in company code B.While raising inter-company invoice to company code A, we are facing problem.
In replenishment delivery we have 10 line items. But when we try to do inter company invoice through VF01/VF04 we get following log
XXXXXXXXXX(delivery Number) 000000 Customer XXXXX: Customer master table KNVV is missing (VF-022)
XXXXXXXXXX (delivery Number)000010 The bill-to party could not be determined (VF-047)
XXXXXXXXXX (delivery Number)000010 The payer could not be determined (VF-048)
With this first line item from delivery is not flows to invoice & if we saves this invoice then it is get saved with account determination error as some of the data does not comes into invoice header like account assignment group for customer, Payment term, destination country,region, tax classification for customer etc. That means invoice gets created without first line item from delivery with account determination error & so,no accounting document gets generated.
I checked customer master for all SP,SH,BP,PY they are correctly maintained.This was working fine few months back, but not working now.
If anybody had come across such kind of scenario, your valuable inputs will be highly appreciated.
Thanks & kind regards,
Ganesh Palatshaha

Hello
Kindly check the sales area of customer involved, whether the customer maintain with sales area for STO.
If that is note the case the refer following link:
- Error VF 047 & 048 while creating Inter company billing
Regards
JP

How to write error log while creating invoice and avoid implicite commit

Hi,
I've have written code in exit RV60AFZZ in which I check for some possible errors while invoicing via VF01/VF04. If conditions are met then we create error message and display it to the user. As result we had a lot of missing SD invoices in FI when we did batch/mass invoicing. I've opened OSS note and SAP support team wrote that using statement MESSAGE is forbidden in UE. It can lead to implicite commits.
Do you have some example how to write error log for invoincing in VF01/VF04 transactions?
Thanks

@ sri nath. Please read post before answering. I wouldn't be posting trivial questions. As I wrote before it doesn't work. Also SAP support would not answer to the question in my OSS.
In VOFM, SAP is using routine VBFS_HINZUFUEGEN_ALLG to write to error log.
Mine is something like this in ue:
      PERFORM ZVBFS_HINZUFUEGEN_ALLG
                 USING VBAP-VBELN VBAP-POSNR 'ZSD' 'E '600'
                       SPACE SPACE SPACE SPACE.
(we have custom message class)
As result XVBFS and VBSK are filled with error, but posting is also done. Error log is filled but invoice is created and posted in FI.
That is not OK.
thanks

Error message VF 217 when creating downpayment request in VF01

Dear Experts,
We use milestone billing. I did all the necessary settings in customizing.
Here is an example for a billing plan
billing date    date description   billing rule   date category billing type
28.02.2010 0009                      5                 04                   FAZ
28.03.2010 0008                      3                 02
When I create a FAZ (downpayment request) in VF01 or VF04, SAP says "check the log" . In the log I get the error message VF 217 "For downpayment requirements, only billing rule 4 or 5 can be used". If I check the item data of e.g. item 10 the billing rule is indeed "5". So I wonder, why I get this error message in the first place. Do you have any idea, how I can supress this error message?
If I create the FAZ manually via VF01/VF04, I get this message, but I can still save and process the FAZ without any problems.
But we need to create the FAZ via the POS interface (Retail). So when the interface gets this error message, it actually thinks that the FAZ can't be created. This is causing us problems. Therefore we need to supress the error message.
Thanks a lot in advance!

Hi Mueller,
I think in that case the problem is in billing rule in billing plan type.
Goto OVBJ--> select billing plan type (For ex. 01 - Milestone Billing) --> Please maintain billing rule 4 or 5 --> save it.
In downpayment
Option 4, We use for % based,
Option 5, We use for value basis
After doing thi change, I think your issue will get resolved.
Please try and revert back with your findings.
Regards,
MT
Edited by: M T on Feb 28, 2010 9:11 PM

Billing Document not getting release to Accounting. (VF01 and VF04).

Dear All,
I am facing an Urgent Issue. The User is Generating Invoices using VF01 and VF04. The Invoices is getting generated but not getting released to Accounting. When the User goes in VF02 or in VFX3 and then releasing the Billing Document. The Account Detemination is correctly maintained and G/L is also getting determined.
Please could you advice what may the Issue. Your Urgent Help is appreciated.
Thanks.
Farhan.

Dear Alan,
Yes I got the error message by pressing SHIFT + F4. Invoice Generated but no Accounting Document Getting Generated. A Balance has occured in Transaction Currency AED with the following details.
Technical data
     Tech. data details
      Client
      Group Number
      Sales Document Number                  0004803850
      Item Number of the SD Document         000000
      Schedule Line Number                   0050
      Counter in Control Tables              00
      Message Identification                 VF
      System Message Number                  050
      Output Type                            W
      Message Variable 01                    0004803850
      Message Variable 02
      Message Variable 03
      Message Variable 04
Detail
Diagnosis
     A balance has occurred in transaction currency 'AED' with
     the following details:
     Exchange rate '00', amount '         8,600.00-' and
     currency key 'AED'.
     The data in the transaction currency were transferred from
     the calling application.
System response
     Your data cannot be processed in FI.
Procedure
     The error is probably in the calling application.
nical data
Tech. data details
Client
Group Number
Sales Document Number                  0004803850
Item Number of the SD Document         000000
Schedule Line Number                   0702
Counter in Control Tables              00
Message Identification                 F5
System Message Number                  702
Output Type                            E
Message Variable 01                    00
Message Variable 02                             8,600.00-
Message Variable 03                    AED
Message Variable 04
Group Type
      Group Type
Same error I am getting when I am releasing the Billing Document to Accounting in VFX3.
But When I generate the Invoice using VF01 its getting released to Accounting.
Please advice why the Issue is only coming in VF04 Collective Invoice and in VFX3.
Your Urgent Help is appreciated.
Thanks,
Farhan.

Error in VF04

Similar Messages

Maybe you are looking for