Auth. Object for Document Type -- Post a Park IC Doc

[Former Member]

I am in need of cotrolling the following:

1) UserCC1 will park an InterCo doc with 2 lines (credit to CC1, debit to CC2)

2) UserCC2 should go ahead and post this newly park document

3) UserCC2 should be able to post ONLY the InterCo park documents associate with his/her CC.

4) UserCC2 should NOT be able to post any other doc on any other CC.

I cannot make #2 to work!

I have concluded that in oder to control it, I need an Auth. Object for CC (which I have already) and another Auth. Object that conttols 'Docyment Type'.

Do you know what Auth. Object controls 'Doc.Type'?

Best regards,

Tom

[martin_voros]

Hi,

you can use F_BKPF_BLA. It works with authorization groups assigned to document type. Don't forget that it's optional check and if document type does not have any group assigned then this authorization check won't be executed. Also if standard objects don't work you can always use FI validations to perform custom authorization checks.

Cheers

[Former Member]

Hi Martin, thank you for your reply!

Yes, I am in the process of 'controlling' both CompCode CC (F_BKPF_BUK) and DocTypes DT (F_BKPF_BLA).

I am having a specific DocType that the users should be able to post to another CC!

So I am going to create an Auth. Group for that specific DT.

I'll inform you for the results.

Yes, I thought about the FI Validations (GGB0), but since I am having way too many CC's, it will be a rough maintenance ...

Best regards,

Tom

[Former Member]

The Auth. Object for Doc.Type is F_BKPF_BLA and the Auth. Object for Company.Code is F_BKPF_BUK, how can I force the 'checking' of BOTH Auth. Objects to take place in parallel?

Now, the checking is done 'serially' and I cannot 'capture' the pair values of CC's (Company Code) and DT's (Doc.Type) that MUST be met in order for someone to post a parked document!

Could a Transaction Variant (SHD0) be a possible solution?

Best regrads,

Tom

[martin_voros]

Hi,

you can't force parallel check on 2 fields. The only way how to do it is to have those fields assigned to one authorization object. So maybe you will have to use FI validations and define your custom object. Not sure how transaction variant could solve your problem.

Cheers

[Former Member]

This message was moderated.