cancel
Showing results for 
Search instead for 
Did you mean: 

Error when release cancelation billing (VFX3) - "Required field AWSYS was not transferred in parameter ACCREV"

Former Member
0 Kudos

Dear SD Consultants,

Need your kindly help:

I found this error message when i want to release Cancellation Billing (VFX3), then appear this Error message:

"Required field AWSYS was not transferred in parameter ACCREV".

Usually when i run cancellation billing, it will automatically release to accounting.

But for this case, the accounting document wasn't generated and the error message appear, although when i want to release again via VF02, the same error message appear.

I found SAP Note 367636, but i don't think the condition suitable with my problem.

Anyone has experience the similar case? Please sharing with me.

Thank you.

Accepted Solutions (0)

Answers (4)

Answers (4)

Shiva_Ram
Active Contributor
0 Kudos

Why you think the OSS note does not suit your scenario? Can you provide the details for it. It looks for this error description, no other notes available. So go ahead and implement the code mentioned in the note. Note that OSS note 339928 must also have been implemented in your system.

Regards,

Former Member
0 Kudos

Because in the OSS note 367636 prerequisites condition related to upgrade while in my condition the upgrade already implemented since several years ago and also in the OSS note has correction instruction #231899 valid from 46A - valid to 607 while in my condition it's already 700. So i don't think it's suit to be implemented in my system. Any suggestion?

former_member184701
Active Contributor
0 Kudos

dear,

if you want to fix the problem you have to work with your sap basis / technical team (or request relevant specialist).

your "i don't think" doesn't help as we see here.

regards,

Former Member
0 Kudos

Yes, this explanation which given after i have discussed with the basis team.

Anyway, FYI, in billing data the VBRK-LOGSYS was blank, and after i entry that field (via table) then release was successfully executed without error.

But it was occured only for several billing while in another billing where VBRK-LOGSYS also blank can also successfully release.

So, i just continue to analyze the root cause, why for several billing the  VBRK-LOGSYS was blank which some of them can be released and the other can't released.

Thanks & Regards.

former_member184701
Active Contributor
0 Kudos

dear,

i would look  who created those documents and :

1. try to replicate it in TST client (under that/those user(s) name);

2. check out that / those user (s) authorizations;

3. check out the dumps by ST22;

4. check out the user-exits which may impact;

5. check out the update requests by SM13;

6. make sure all transports are in place (may be someone changed the relevant config or some codes)

7. take abaper and debug it

do something, do not sit !

Former Member
0 Kudos

1. try to replicate it in TST client (under thta user name); --> all the transaction was created by the same user and no error occured for new creation transaction

2. check out that / those user (s) authorizations; --> all transaction created by 1 user ID

3. check out the dumps by ST22; --> there's no runtime error

4. check out the user-exits which may impact; --> on going

5. check out the update requests by SM13; --> No update records found

6. make sure all transports are in place (may be someone changed the relevant config or some codes) --> on going

Thank you.

former_member184701
Active Contributor
0 Kudos

dear,

delete that user ID and create it again. check for new documents.

regards,

Former Member
0 Kudos

Hi Dear,

As suggested above please take the help of Basis team to implement the Note and to thorough testing in development client if it is fine then you can transport the same to your production server, and also check the below thread

http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/in-vfx3-awsys-was-not-transferred-in...

Best Regards,

Former Member
0 Kudos

Dear

Dear this kind of problem rarely occurs and this generally occurs due to change in LDB i..e Logical Database. Try to check field VBRK-LOGSYS is not filled in the particular SD invoice.
A change has been made in the table T000, the logical system has been filled in.
If you have older SD invoices, that have not been released to accounting, the field is missing in these documents Just fill in the name of the logical system from T000 into VBRK-LOGSYS for the document that caused the problem. After this you can release the document to accounting.

And go to VF02 in Document header data and Change Billing date in and post ...

Thanking you

Ashish Mishra

former_member184701
Active Contributor
0 Kudos

dear,

i would recommend to talk to basis guys (also request them about that note 367636)

regards,