cancel
Showing results for 
Search instead for 
Did you mean: 

SAP_Condition Contract_SY530 Exception error when running WB2R_SC

pierpaolo_parma
Explorer
0 Kudos

Hi experts,

i have the aim to save accruals and settlements documents into the WB2_D_BVDETAIL table; in order to do that, i've set the "Z" entry into the below customizing path.

Once set, everything works well; whenever i run the WB2R_SC the system stores the documents accordingly.

There is anyway a specific case in which i got an error.

I set a condition contract having material codes specified into the standard table "V 163 Condition contract / Material",

When running the WB2R_SC, the system creates the accrual document but it get at the same time the error "SY530 - An exception was raised"

Due to that, the WB2_D_BVDETAIL table is not updated.

Do you have any hint on that? why this table does not work with agreements having materials specified into its condition?

Thanks and regards

Pier Paolo

Accepted Solutions (0)

Answers (2)

Answers (2)

gvictor
Active Participant
0 Kudos

Hi pierpaolo.parma ,

SY 530 suggests that you have an ABAP exception, I would recommend that you debug or call an ABAP resource to find the root cause, at this point it can be many things but I doubt that the only issue is the "Save detailed Statement data" parameter.

In the mean time, try also to change the parameter to Y instead of Z, unless you really use the Accrual deferral.

Regards,
Gauthier V.

Lakshmipathi
Active Contributor
0 Kudos

In general, if the document type is not assigned in SPRO, system will trigger this error. So check whether the document type is assigned in SPRO > LG > Settlement Management > Condition Contract Management > Condition Contract Settlement > Define and Configure Profiles for Business Volume Determination > Select Profile > Additional Business Volume Tables

If assigned but still have an issue, check SAP note 3382393

pierpaolo_parma
Explorer
0 Kudos

thx for your reply Lakshmipathi,

I don't think is a matter of document type because the error occurs only in case of contracts having the condition types defined at material level (table "V 163 Condition contract / Material").

In all other cases (for which the accrual document type is the same), everything works; it seems there's such kind of issue when transferring the data into the WB2_D_BVDETAIL table if the agreement has materials inside of it.

I already followed the note 3382393 that just suggest to set the "Z" entry in customizing (and i made it)

Thanks

Pier Paolo

Lakshmipathi
Active Contributor
0 Kudos

When you create a discussion and add further updates, please do so under "Comment" and not under "Answer" as you were not answering but providing additional information as asked by the member. By doing so, a mail will be triggered to who you respond. By the way, I have converted your answer to comment