The following content in this document is going to describe on what condition transaction MRBP is going for posting date re-determination

I just came across an intresting problem while working on an issue related to MRBP posting the invoice.

The problem is like this :

1. The user uses Transaction MIR6 for scheduling the invoices in the background which is later picked by transaction MRBP for posting.

Image1.png

Image2.png

2. Now in transaction MRBP we have an option for Posting Date Determination. lets say we select the value as “2” here which means ( Determine Posting date automatically, if date is invalid )

/wp-content/uploads/2014/05/image3_447869.png

/wp-content/uploads/2014/05/image4_447871.png

3. Now with this option system will try to redetermine the first posting date which is open in current posting period in transaction OB52

/wp-content/uploads/2014/05/image5_447875.png

4. Now how system is determining this date?

a. Firstly system wll check the posting date already found in the invoice is valid ( for posting ) or not with the transaction OB52.

b. it takes the month (monat) of the posting date already available with the invoice and call function module

    FI_PERIOD_CHECK with the KOART and KONTO value as “+” for the variant.

    Now the option Alternative posting date will only be used if the variable “o_error” will become ‘X’.

/wp-content/uploads/2014/05/image6_447876.png

c. if it finds it is open, it will proceed with out changing the posting date of the invoice.

Summary is : when using the MRBP transaction look for the period on OB52 with KOART and KONTO value as “+’. If the period is not open then only system re-determines the posting date, that is the values for Alternative Posting date wil be considered.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply