Invoice Posting in Background Baseline date error

[Former Member]

We have the following scenario:

Create PO with multiple skus

Receive multiple GRs for either one PO line or a combination of them

Receive multiple Invoices from Vendor either by GR or otherwise

Lot of times invoice is received before GR and we are using OpenText wherein we enter the header information (Vendor number\date\PO number\Gross amount)

The standard OpenText functionality is mapped to MIRO transaction where this data is passed on to ECC.

Because of our scenario of Invoice received before GR, most of the Invoices go into exception queue and need to be manually adjusted in the Invoice lines. To avoid manual intervention I am thinking of using MIRA instead of MIRO in the background. The invoice header will be passed over to MIRA and the document parked. The batch job for MRBP (RMBABG00) will try to match the GR as and when it comes to the IR document.

I hope my understanding about the MIRA\MRBP transactions is correct.

I am testing a simple scenario wherein we receive GR and park invoice through MIRA. However, it is failing because the baseline date on the invoice becomes blank when the MRBP transaction runs. I get the following error "Baseline date for payment does not exist" (message number Message no. M8356). I have made sure that the payment term and baseline date both are present when I enter in MIRA. Also, checked the payment terms and it does have the default for baseline date set to document date.

I reviewed a note 154405 which seems to be applicable to this, but am not sure as it is dated 1999.

Any help will be highly appreciated.

[Former Member]

we had a similar issue in Open Text VIM.

we had created a new payment term which had the default  baseline date set as 'NO DEFAULT'  and we used a substitution to fetch the baseline date. It worked fine when the postings were done online but faced the same error message during background execution.

we removed the default date option as 'NO DEFAULT'  and set it as 'ENTRY DATE' then the issue got solved.

Since the Payment term anyway had a substitution for setting the baseline date, it got populated as per the requirement.