Skip to Content


Hello All,

We have requirement to retire a asset hence we used the BAPI BAPI_ASSET_RETIREMENT_POST. everything works fine when we have all the required authorization. But due to security restriction our client is not willing to give authorization to user to Retire an Asset as it is sensitive. Hence we advised them there is importing parameter in the BAPI GENERALPOSTINGDATA-USERNAME which holds the SY-UNAME if we can have a TVARV entry to re-write the SY-UNAME to BATCHID as it has all the needed authorization. But when we tested this, the bAPI does n't consider the BATCHID at all and throws a error message with Auth restriction. As per our understanding once we change the SY-UNAME it should consider the value BATCHID for Auth Checks.

Please let us know whether we are missing any point here also please suggest on any altermatives


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers