cancel
Showing results for 
Search instead for 
Did you mean: 

VFRB / Billing output issues

Former Member
0 Kudos

When running retro billing VFRB, entries in NAST (Output) table has been updated with entries even before the debit or credit documents have been created. So we have entries in NAST with object id $000000001 and so on instead of the correct billing document number. This has been a one time issue.

Due to which we face issue when the batch job for output is processed RSNAST00.

1. $000000001 records ends in error, this is Ok since these are junk records

2. few of the document outputs is not getting process (all billing documents types included), for exaple there are 100 documents to print only 97 gets printed. the balance 3 does not get printed. The 3 documents does not get processed by the program RSNAST00 when the variant considers all open document, the program ends in error because of the junk records. the documents gets printed if the document number is given explicitly.

3. When the program is processed next day the new billing documents for the day are processed correctly, but the previous days 3 documents does not get processed. and a few documents of the current day is also not processed, the program ends in error because of the junk records.

4. this results in a a huge set of outputs not processed after a few days.

Has any one seen similar behavior with VFRB, and with the RSNAST00 program.

Accepted Solutions (0)

Answers (1)

Answers (1)

Jelena
Active Contributor
0 Kudos

It seems that obvious solution is that you need to delete the "junk records". Look up the OSS notes - perhaps there is some solution already for NAST clean-up. Otherwise it shouldn't be difficult to create a short program for that.

Even if you're "OK" with the records not being processed, it is quite clear that these records are causing interruption in the program's flow.

As a work-around, you can exclude the "junk records" using 'Object key' parameter when running RSNAST00, but deleting such records would be an ultimate solution.

I'd also look into how did you end up with such records to begin with. It is a highly unusual effect.