Question:
Data View is missing for the Object C_APO_PB
when user runs the transaction, It is not through and giving the below as per SU53.
The following authorization object was checked:
Object C_APO_PB APO 3.0 Authorization Object: SDP Planning Books
Object class APO APO Authorization Objects
Field Value
Activity
03
Data View
DP_Materials
Planning Book
DP_Materials
1. gave * for the planning book,still it is asking dp_materials missing in Planning Book.(Infact Dp_materials exist in Planning book.)
2. Dont see the data view for the object c_apo_pb ,But SU53 gives messsage that dataview dp_materials is missing.
I feel there must be some OSS note to applied.
Let me know,if you know any OSS Note with reference to this issue.
Any suggestions and ideas are welcome.
Note : we have gone for upgrade to 4.10 from APO 3.0A. Is this could be an issue?
Answer:
it may be that the * is evaluated as a "*" rather than a wildcard. Does it act the same if you enter the exact planning book text string?
Answer:
We did the same APO upgrade and ran into the same issue. Ensure that you have run through SU25 except step1 unless you really want to overwrite all of you SU24 changes. You then can update the object C_APO_PB in SU21 to include APO_DVIEW.
Hope that helps.
Answer:
hi,
We had the same problem after we upgrade APO 3.OA to SEM 4.1, it say that some inconsistence may happen .
This inconsistency is because in Role and in SU24 data there are only
2 fields for C_APO_PB, as it was in APO 3.0.
But in APO 4.1 it has 3 fields for this object, as per data from SU21.
You can see this if you run su24 for SAPAPO/SDP94 and display the
default field values as only 2 fields are displayed however this object
has 3 fields.
A correction report is available to fix this problem.
It is called Z_USOBT_C_REPAIR and is attached to this message.
As title you can use whatever you like, we suggest to use "Report for
removing inconsistencies in table USOBT_C". If you want to use the
program in other systems, too, you should save it in a transportable
development class.
In the selection screen you only need to enter the transactions you
want to identify inconsistencies for (field "TRANS"). In your case the
generic entry /SAPAPO/* may be useful. If you keep the option "TESTMODE"selected the found inconsistencies are only displayed, but no database
updates are performed. They take place as soon as you deselect the
test mode.