RUNALLOCATION status "ok" in spite of rejected records by workstatus feature.

[Guillaume_P]

Hello experts.

I've looked for a "known issue" like mine with no success.

After a mistake in the planning process, we've run an allocation package on a slice of data "Approved" with the workstatus feature.

The status of the package is "succeeded" so we've initially thought all was fine.

Unexpected results has made us look inside the detailed log of the run (downloaded from UJFS t-code) -> we can see that :

-----------------------------------------
WHAT data: 40 records.
-----------------------------------------
Existing WHERE data: 25 records.
-----------------------------------------
USING data: 25 records.
-----------------------------------------
TOTAL data: 5 records.
-----------------------------------------
--Records succeeded to write back : 0
--Records failed to write back :--Records failed to write back : 225

We are using BW 7.50, SP16 (EPM componants are included).

If the issue is "local" to our code I can provide it.

Is it something known that rejected records at write back step during the allocation run are not "triggering" a global "Failed" status ?

Thanks in advance for your feedback.

Rgds.

G.

[former_member186338]

Correct, package status is succeeded.

Allocation is just one operation of script logic execution... And not written can be seen only in log...