on 04-02-2013 4:27 AM
Hi Experts,
I am using t-code REEXF_28 and noticed that the default baseline date that the system puts on the cleared item when I simulate the transaction is the document date. This should not be the case since based on the configuration of payment terms the posting date should be the default baseline date.
The master data used has due immediately as payment terms. Invoice Posting has blank payment terms.
I've checked the configuration of Payment terms via OBB8. The posting date was ticked as the default baseline date.
I try changing the default for baseline date just to check if the configuration is working but unfortunately it does not change the date that is defaulted on the baseline field via t-code REEXF_28.
So my question are:
1) Is the configuration in OBB8 not work in t-code REEXF_28?
2) How is the default baseline date configured in REEXF_28?
Please help me...
Thank you in advance!
Hi Natalie,
While posting an invoice in Fb60 or Fb01 the baseline date is derived as per the settings in OBB8. Whereas for payment documents (F-28/REEX_28 etc.) the baseline is defaulted as document date irrespective of the OBB8 setting.
I think this is because, the baseline date is needed for invoice documents for calculating the net due dates. Whereas they are not significant in payment documents, so defaulted as document date.
Do you have a specific requirement for getting a baseline date in payment document? If so can you brief about it?
Hope it helps,
Thanks,
Akshaya Lakshmi.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Ms. Akshaya,
Thank you for the information. Users want the baseline date when using REEXF_28 to be modifiable before generating the payment documents. They will use this field to know the clearing date of the payment as against the invoice specifically for collections posted late in the system, since clearing date will not be helpful.
Example:
Check dated March 26,2013;deposited to the bank April 1,2013;OR preparation: April 2,2013
Closing of period 3 done on March 31,2013
Upon execution of REEXF_28, user will input as Doc. date: April 2,2013 Posting Date: April 1,2013 and the system will automatically input April 2,2013 as baseline date, but the user wants to have the baseline date equal to March 26,2013 so that they will know that the payment was made on that date.
Is this possible?
Thank you so much.
Hi Natalie,
Thanks for the details. the field baseline date will not be populated in REEXF_28 during execution. Hence there is no scope of changing the same.
So as a ork around we can try the following options with the data given in example:
1. Posting date : 01.04.2013 (OK)
2. Document date: 26.03.2013 (As the check was received on 26th Mar only)
3. Baseline date: 26.03.2013 (same as above as per standard SAP)
4. Value date: 02.04.2013 (As cheque is deposited and will be processed only from this date)
Else
1. Posting Date: 02.04.2013 (OK)
2. Document date: 02.04.2013(OK)
3. Baseline date: 02.04.2013(Same as above)
4. Value date: 26.03.2013 (Which can be used for your tracking purpose with the banker)
Else.
In the field clearing text (AUGTX)-the last field in first box of REEXF_28, the date 26th March 2013 can be entered as text and tracked.
Let me know if any of the three workarounds can work for you
Thanks,
Akshaya.
Hi Ms. Akshaya,
Thank you for the work around you mentioned.
1st:
1. Posting date : 01.04.2013 (OK)
2. Document date: 26.03.2013 (As the check was received on 26th Mar only)
3. Baseline date: 26.03.2013 (same as above as per standard SAP)
4. Value date: 02.04.2013 (As cheque is deposited and will be processed only from this date)
-document date can not be changed to 26.03.2013 since they used this date to determine when the OR was issued/prepared
2nd:
1. Posting Date: 02.04.2013 (OK)
2. Document date: 02.04.2013(OK)
3. Baseline date: 02.04.2013(Same as above)
4. Value date: 26.03.2013 (Which can be used for your tracking purpose with the banker)
-they want the date to be reflected on the customer line item. Value date is only available on the cash account entry right?
3rd:
In the field clearing text (AUGTX)-the last field in first box of REEXF_28, the date 26th March 2013 can be entered as text and tracked.
-this might work but subject to human error since text is just an input field and this can be changed by any users authorized to change documents. But I will ask the users if they want the date to be on the text field.
Thank you so much.
Hi Ms. Akshaya,
Actually work around #3 is still pending approval of the users. I think this is the best way based on the users business process to address the issue. I also informed the users of the pros and cons of this work around.
I tagged my discussion as answered since you answered my questions below correctly.
1) Is the configuration in OBB8 not work in t-code REEXF_28?
2) How is the default baseline date configured in REEXF_28?
Thank you.
Hi,
Basically the Field baseline date is meant to calculate the due date and thereby arreas of payment can be calculated. So it is relevant for Customer invoice creation.
So for payment related transactions(F-28/REEXF-28), the baseline date calculation from OBB8 does not work.
2) How is the default baseline date configured in REEXF_28?
The baseline date in REEXF-28 is not configured and is resulted from standard SAP program. If you notice the due date field also, it would be copied from Baseline date. Since these dates are irrelevant in payment document for the standard functionality, SAP has configured them so.
But your requriement is to track the cheque received date. Whereas SAP did not foresee this as a requirement and has not provisioned for this customization I believe.
Hi,
Can you check whether that Payment term is marked for customer or not?
Baseline date must be as per payment term configuration only.
BR, Kavita
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.