Confirmation on partially released network

[] [] [] []

Symptom
You carry out a confirmation on a network activity with the system issuing error message BS002 “Actual activity allocation is not allowed” in the cost determination.
Other terms
CN25, CAT5, COFC, BS002
Reason and Prerequisites
The symptom only occurs if the network has the status “Partially released”.
Solution
The system response depends on the account assignment type of the network that is defined in the network type.
The network is activity-assigned:
In this case a confirmation on the network activity should be allowed if the business transaction has status “Released”. If the system still issues error message BS002 you have to implement Notes 622456 and 638826 or import the appropriate support packages.The network is header-assigned:
In this case, a confirmation on the network with status “Partially released” should not be allowed. However, up to and including Release 4.6C the system did not issue any error message in the cost determination. As of Release 4.7 the program logic analogous to a direct activity allocation (Transaction KB21N) on the network is at this point.
If you want to keep the program logic of Release <= 4.6C in your system, implement the program modification from this note. Afterwards, the system supresses this check from the status management and does no longer issue error message BS002.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment