Bapi_acc_document post is not calculating baseline date based pymnt terms

Hello friends,
Im using bapi_acc_document_post to post db and cr note and i m passing payment terms in the input file but the bapi is not calculating baseline date .
pleasee let me knw the solution.
Regards,
Sunny

that's the disadvantage of bapis and direct input in opposite to BDC. So use "old" rfbibl00 with batch input!
A.

Similar Messages

Posting Document not created (export data missing)

We are working on ECC 6.0 and during creation of Cancellation Billing document type IVS for the Intercompany billing, the document did not create Accounting document giving the Posting status as G - Posting document not created (export data missing). However checked the Foreign trade data and the system states that Foreign trade is complete.
Can any one suggest the solution for this?
Thanks.

Hello Mohammad,
About this issue, the incompletion of this cancellation document
arises might because the reference delivery has been archived/deleted.
This is likely due to your current copy control settings (VTFL).
If you have set ' ', in the export determination field this means that
there is a common 'exnum' key between the delivery and billing documents
LIKP-EXNUM & VBRK-EXNUM are the same.
The result of deleting the delivery is that you also delete the FT data
for the delivery, Because the billing document and delivery share the
same foreign trade table entries, you have in effect deleted the FT data
of the billing document too. This would most likely go unnoticed but if
you then cancel the invoice the system has no FT to copy into the new
cancellation billing document, which leads to this issue.
Firstly you should set the export determination flag in the copy control
of the delivery & billing documents. This will avoid this issue in the
future. Set it to to 'A' or 'B' depending on your requirements.
For the incomplete cancellation billing document, you could use userexit to
set it as complete:
You can use transaction CMOD.
Create a project for example FT project button create short text: ....
drop button Enhancement assignment & save use for example local object.
Use the F4-help for Enhancement and look for V50EPROP.
Drop button Components:
here you will find EXIT_SAPLV50E_005 and EXIT_SAPLV50E_006
In the userexits doubleclick on the includes ZXV50U05 and ZXV50U06
The coding in the userexits should be: C_COMPLETE = 'X'.
Afterwards activate generate ... and save.
The development class is VEI.
Please also check note 118573 which explains the FT user exits.
Regards,
Alex

Baseline date in payment terms

Hi experts,
There're 4 kinds of baseline dates in payment terms: no default, posting date, document date & entry date. I have gone through the relevant thread & tested in the system.
However, I found no differences among them, i.e. no matter which baseline date is selected, billing date automatically captures actual delivery date from delivery when creating invoice.
Why? Is there something wrong?
Plz help. Many thanks.

As I already mention, baseline date for payment is the date from which the terms of payment apply.
So,
- No default for the base date, this Indicates that no default value is required for the baseline date for payment. You then have to enter the base date manually during document entry.
- Propose posting date, this Indicates that the posting date is to be proposed in the base date field during document entry.
- Propose document date, this indicates that the document date is to be proposed in the base date field during document entry.
- Propose entry date, this indicates that the entry date is to be proposed in the field Base date during document entry.
Where,
Base Date is the date to be entered in the header of a document.
Posting Date is the date on which a business transaction is transferred into one or more accounting ledgers on document entry.
Document Date is the date on which the original document (such as vendor invoice) was created.
For understanding refer following links:
[Terms of Payment|http://help.sap.com/saphelp_40b/helpdata/en/96/8b3fc643ce11d189ee0000e81ddfac/content.htm]
[Baseline Date for Payment|http://help.sap.com/saphelp_46c/helpdata/ru/e5/0783804acd11d182b90000e829fbfe/content.htm]
Hope this can assist you.
Thanks & Regards
JP

Setting baseline date based on a specific payment term

Hello everybody,
I have a requirement where i have to change the baseline date in MIRO based on a specific payment term. For ex: out of 3 payment terms A, B and C which all take the same base line date set in MIRO, i want to change the base line date for say condition B only.
I can't find the 3 different payment terms in any exit or BADI. I just get the value in ZTERM as say 'A1' which is the main installment term.
Could anybody tell me how I am supposed to do this?
Regards,
Ritwik Rajkumar

Dmytro has made some excellent suggestions. If it were me, I would rebuild the table into partitions based on the new column EXPIRATION_DATE assuming that the vast majority of the records are to be "expired".
However, I would first set a local variable from sysdate rather than use it in the SQL so that you don't have any context switching to query sysdate for each record AND preserve the same timestamp for all records updated:
declare
V_TIMESTAMP date := sysdate;
begin
update MY_BIG_TABLE
set EXPIRATION_DATE = V_TIMESTAMP
where nvl(EXPIRATION_DATE,V_TIMESTAMP) >= V_TIMESTAMP;
end;

Error When Trying to POST: Method not implemented in data provider class

Hi Experts,
I have created an Odata Service using Netweaver Gateway Service builder. I am using Advanced Rest Client to test the service. I can successfully GET my data, but I run into issues when I try and POST new data.
When trying to POST, I used the GET method to get the x-csrf-token, and added it to my header. I also updated the body XML with the data that I would like to POST. However, after sending the POST request, I am getting a "500 Internal Service Error" with the xml message "Method '<OdataServiceName>'_CREATE_ENTITY" not implemented in data provider class".
Any help on this would be greatly appreciated. Thanks!

Hi Kelly,
Can you share screenshots of the error? Maybe something wrong with payload :can you share the same also? Did you try to debug it by putting a breakpoint in the CREATE_ENTITY method in the backend? Any luck?
Regards,
JK

Default for baseline date in Payment terms

Hi All,
Can anyone please explain me the options in OBB8 default for base line date 1. No Default 2. Posting Date 3. Document date 4. Entry Date while creating payment terms with examples.
It's very very very Urgent!!!!!!!!!!!!
Thanks in advance.
Boppana

Hi,
The following are the examples:
1. No default: Self explanatory, hence system does not consider any default value to start for calculation of due date. The baseline date has to be entered manually at the time of Invoice creation.
2. Posting Date: The date of entry in the system 31-Jul-11 (after two days).
3. Document Date: The date on the physical Invoice which we key in at the time of Invoice entry. Say for example 25-Jul-11.
4. Entry Date: This is the system date i.e. todayu2019s date 29-Jul-11. This date is internal in the system and not controllable or editable.
To summarize, for 2, 3 & 4 the system defaults the baseline date (changeable) at the time of Invoice entry but, for 1 system does not default any baseline date.
Regards,
Kiron Kumar T.

Day Limit, Fixed day/Additinal months & Baseline Date in Payment Terms-OBB8

Hi Gurus,
Please put some light on the following:-
1. What is the relation between Day Limit & Baseline Date.
2. What is the use or significance of Day Limit as far as Payment Term for Vendor/Customer is concerned?
Thanks & regards,
CS

Hi,
The day limit is used to process the document for due date determination based on the baseline date (document date, posting date etc. which is specified in payment term) of the documnt.
For example, if you have defined first payment term P000 with the day limit as 15 and second P000 with day limit 31, then the documents having baseline date 15th or before will attract first payment term for due date calculation and documents with baseline date after 15 will attract second payment term for due date calculation.
I hope the things are clear to you now.
Regards,
Gaurav

BaseLine date different from Terms Of Payment Date

Hi,
My client posted 3 documents dated 23.12.2009,17.12.2009,14.12.2009 respectively. The terms of payment has been set to accept document date as default for the baseline date. This means that the baseline dates for the documents should be same as 23.12.2009,17.12.2009,14.12.2009 respectively. However, the system has set 31.12.2009 as baseline dates for all MIRO documents. I have already checked Terms Of Payment ,Vendor Master and the posted documents.
Can anyone please provide any clues to this problem?
Thanks In Advance
Regards,
Payal Saxena

Hi Payal
Request you to check settings for PT in OBB8
Also, refer to this thread - Baseline date in payment terms_reply the question for FI experts
If the problem still persists, you will require a user exit.
Rgds,
Zub

Posting date as Baseline Date in Residual item

Hello,
While clearing a document with Residual Clearing method through F-28 system is automatically proposing end of the month as Baseline Date for the residual item (newly created item for the balance amount), whereas we want it to be the posting/document date but not the monthend as proposed by the system. Eventhough we have selected the option for default baseline date as posting date/document date in Payment Terms, system is proposing monthend date as baseline date for the residual item. I have set payment terms in customer master record as 0001 (immediate payment).
Because of the settings made for default baseline date in payment terms (SPRO/AR-AP) system is proposing document date as baseline date for new documents being posted, but we are facing problem only in case of residual items (new item created for the balance amount while doing residual clearing).
Please let me know the procedure to change the settings, so that posting/document date will become default baseline date for the newly created open item while doing residual clearing.
Thanks in Advance

Hi,
Try to take a look the setting of the following transaction,
IMG> FA> AR & AP> Business Transactions> Incoming Payments> Manual Incoming Payments> Define Tolerances
See what has been set for payment term for Residual Items.
Regards,

Baseline date calculation

Hi,
We have a requirement to exclude non-Business days while calculating Baseline date(for the Accounting Document created on saving the Billing document)
Currently the Baseline Date being populated in the Accounting Document is Document date + 5days(including Holidays).
For eg
Current Scenario
Document Date: 12th Feb 2008
Baseline date: 17th feb 2008.
Requirement:
Document Date: 12th Feb 2008
Baseline date: 19th feb 2008(Excluding Sat & Sun).
Request you to share useful info in this regard.
Thanks
Binu

Hi,
Use user exit RV60FUS5 for these base line date calculations.
Thanks
Krishna.

Baseline date calculation excluding non-Business days

Hi,
We have a requirement to exclude non-Business days while calculating Baseline date.
Currently the Baseline Date being populated in the Accounting Document is Document date + 5days(including Holidays).
For eg
Current Scenario
Document Date: 12th Feb 2008
Baseline date: 17th feb 2008.
Requirement:
Document Date: 12th Feb 2008
Baseline date: 19th feb 2008(Excluding Sat & Sun).
Request you to share useful info in this regard.
Thanks
Binu

Hi,
Use user exit RV60FUS5 for these base line date calculations.
Thanks
Krishna.

BADI MRM_PAYMENT_TERMS - Baseline date

Hi All,
The requirment I have is to automatically populate the Baseline date based on the GR posting date and Invoice posting date.
While creation of the Invoice in MIRO,
       1) If the GR posting date is greater than the Invoice posting date then the Baseline date should be populated with the GR posting date.
       2) If the Invoice posting date is greater than the GR posting date then the Baseline date date should be populated with the Invoice posting date.
This logic I have implemented in the BADI MRM_PAYMENT_TERMS which works as expected.
But the standard calculation of 'DUE ON' date, Payment terms, Cash discount days are not performing according to the standard functionality and these values do not get displayed.
Why is this getting affected?
Also, please suggest if there is any other way to achieve this requirement without any deviation from the standard functionality.
Below is the code that I have implemented in the BADI.
*----Defining the structure for work area for EKBE table data fetch
TYPES: BEGIN OF TY_EKBE,
          EBELN TYPE EBELN,
          EBELP TYPE EBELP,
          BELNR TYPE MBLNR,
          BEWTP TYPE BEWTP,
          BWART TYPE BWART,
          BUDAT TYPE BUDAT,
         END OF TY_EKBE.
*----Defining the work areas
DATA: WA_EKBE TYPE                   TY_EKBE,          "Work area for History per Purchasing Document table
        WA_DRSEG TYPE LINE OF           MMCR_TDRSEG.      "Work area for Invoice doc items
*----Checking if the Company code is IBTG
IF I_RBKPV-BUKRS = 'IBTG'.
*----Selecting data from EKBE table to fetch the latest GR posting date
    SELECT EBELN
           EBELP
           BELNR
           BEWTP
           BWART
           BUDAT
    INTO WA_EKBE
    FROM EKBE
    FOR ALL ENTRIES IN TI_DRSEG
    WHERE EBELN = TI_DRSEG-EBELN
    AND   BEWTP = 'E'
    AND   BWART = '101'.
    ENDSELECT.
*----Looping at Invoice Doc. Items table into its work area
    LOOP AT TI_DRSEG INTO WA_DRSEG.
      IF WA_EKBE-BUDAT > WA_DRSEG-BUDAT.                 "If GR posting date is greater than invoice date
        E_ZFBDT = WA_EKBE-BUDAT.                         "Assigning the GR date to Baseline date
      ELSEIF WA_EKBE-BUDAT < WA_DRSEG-BUDAT.             "If Invoice date is greater than GR date
        E_ZFBDT = WA_DRSEG-BUDAT.                        "Assigning the Invoice date to Baseline date
      ELSEIF WA_EKBE-BUDAT = WA_DRSEG-BUDAT.             "If Invoice date is Equal to GR date
        E_ZFBDT = WA_DRSEG-BUDAT.                        "Assigning the Invoice date to Baseline date
      ENDIF.
    ENDLOOP.
ENDIF.

Hi,
if you go to se18 and display badi MRM_PAYMENT_TERMS,
in "Interface" tab if you double click on "Example implementation class" CL_EXM_IM_MRM_PAYMENT_TERMS
and then in class interface CL_EXM_IM_MRM_PAYMENT_TERMS, if you display the code of IF_EX_MRM_PAYMENT_TERMS~PAYMENT_TERMS_SET you will find three examples:
METHOD if_ex_mrm_payment_terms~payment_terms_set .
*--- fill all export-parameter ----------------------------------------*
e_zfbdt = i_rbkpv-zfbdt.
e_zbd1t = i_rbkpv-zbd1t.
e_zbd1p = i_rbkpv-zbd1p.
e_zbd2t = i_rbkpv-zbd2t.
e_zbd2p = i_rbkpv-zbd2p.
e_zbd3t = i_rbkpv-zbd3t.
e_zlspr = i_rbkpv-zlspr.
*** Example 1: Setting ZFBDT depending on goods receive
DATA: h_drseg TYPE mmcr_drseg,
        h_budat TYPE mmcr_ekbe-budat.
TYPES: BEGIN OF x_datum ,
           budat LIKE h_budat,
         END OF x_datum.
TYPES: BEGIN OF x_ekbe_gelesen,
           ebeln TYPE ekbe-ebeln,
           ebelp TYPE mmcr_ekbe-ebelp,
         END OF x_ekbe_gelesen.
DATA: h_ekbe_gelesen TYPE STANDARD TABLE OF x_ekbe_gelesen,
        h1_ekbe_gelesen TYPE x_ekbe_gelesen.
DATA: h_datum TYPE STANDARD TABLE OF x_datum,
        h1_datum TYPE x_datum,
        h_ebeln LIKE h_drseg-ebeln,
        h_ebelp LIKE h_drseg-ebelp.
LOOP AT ti_drseg INTO h_drseg WHERE selkz = 'X'.
    SELECT budat FROM ekbe INTO h_budat WHERE
         ebeln = h_drseg-ebeln AND
         ebelp = h_drseg-ebelp AND
         lfbnr = h_drseg-lfbnr AND
         lfgja = h_drseg-lfgja AND
         lfpos = h_drseg-lfpos AND
         vgabe = '1'.
      IF sy-subrc EQ 0.
        MOVE h_budat TO h1_datum-budat.
        APPEND h1_datum TO h_datum.
      ENDIF.
    ENDSELECT.
ENDLOOP.
SORT h_datum DESCENDING.
READ TABLE h_datum INDEX 1 INTO e_zfbdt.
*** Example 2: calculate best payment terms based on manual settings
DATA: h2_drseg TYPE mmcr_drseg,
        h2_zbd1p TYPE mrm_rbkpv-zbd1p,
        h2_zbd1t TYPE mrm_rbkpv-zbd1t,
        h2_zbd2p TYPE mrm_rbkpv-zbd2p,
        h2_zbd2t TYPE mrm_rbkpv-zbd2t,
        h2_zbd3t TYPE mrm_rbkpv-zbd3t,
        h21_zbd1p TYPE mrm_rbkpv-zbd1p,
        h21_zbd1t TYPE mrm_rbkpv-zbd1t,
        h21_zbd2p TYPE mrm_rbkpv-zbd2p,
        h21_zbd2t TYPE mrm_rbkpv-zbd2t,
        h21_zbd3t TYPE mrm_rbkpv-zbd3t.
LOOP AT ti_drseg INTO h2_drseg WHERE selkz = 'X'.
    SELECT zbd1p zbd1t zbd2p zbd2t zbd3t
      FROM ekko
      INTO (h2_zbd1p, h2_zbd1t, h2_zbd2p, h2_zbd2t, h2_zbd3t)
      WHERE ebeln = h2_drseg-ebeln.
      IF sy-subrc EQ 0.
        IF h2_zbd1p GT h21_zbd1p.
          MOVE h2_zbd1p TO h21_zbd1p.
          MOVE h2_zbd1t TO h21_zbd1t.
          MOVE h2_zbd2p TO h21_zbd2p.
          MOVE h2_zbd2t TO h21_zbd2t.
          MOVE h2_zbd3t TO h21_zbd3t.
        ENDIF.
      ENDIF.
    ENDSELECT.
ENDLOOP.
IF h21_zbd1p GT i_rbkpv-zbd1p.
    MOVE h21_zbd1p TO e_zbd1p.
    MOVE h21_zbd1t TO e_zbd1t.
    MOVE h21_zbd2p TO e_zbd2p.
    MOVE h21_zbd2t TO e_zbd2t.
    MOVE h21_zbd3t TO e_zbd3t.
ENDIF.
*** Example 3: Setting ZLSPR depending on currency
CONSTANTS: c_zlspr_r VALUE 'R',
             c_waers_itl TYPE waers VALUE 'ITL'.
IF i_rbkpv-waers = c_waers_itl.
    MOVE c_zlspr_r TO e_zlspr.
ENDIF.
ENDMETHOD.
your case is similar to the first example.
Best regards.

Change baseline date when an accounting document is created.

Hi ,
When a sales order is created and billing is done baseline date in accounting document is copied from billing/invoice date by default. my requirement is to change this baseline date based on some custom logic, This is required because SAP calculates due date based on baseline date. Can anyone help me how this scenario can be handled.
Rgds,
harish

Hi,
As understand from your question, I think its better practice to change the baseline date either manually or automatically from some logic during the billing document creation. This can be done through through the following userexit
USEREXIT_FILL_VBRK_VBRP or
SDVFX004 or
SDVFX008
or
As Mr.Lakshmiprasad explain in his message, make the default setting after concern with FI Consultant in OBB8.
Regards
Goutham

Baseline Date field to be grayed out

Hi ,
I have requirement wherein i want to gray out (not modifiable ) Baseline date field in f-28 .
When u Simulate the document that time the baseline date field is modifialble , i want to make it not modifiable .
Before save it is modifiable i want it to be grayed out.
Please suggest .

HI,
Try this,
This can be acheived through the Transaction Variant.
Transaction Code is SHD0.
In SHD0 you can change the Properties of the Field of a Particular transaction.
Regards,
Sathish

BPC10MS SP12 - Agregate are not calculated

Hi experts,
Hope someone can help on this problem.
I have a YTD model.
We input data on base level,
But, while we try to retrieve any agregate of any dimension, data are not calculated. and data disappeared :-(
Any tips on this to help ?
Tks a lot,
Olivia.

Olivia,
This may seem like a silly question, but do you have the hierarchies defined on the dimensions? Did things work before and just stop working? If you have some screenshots of the dimensions or where you see the problem, that would be helpful, too...
Jeff

Bapi_acc_document post is not calculating baseline date based pymnt terms

Similar Messages

Maybe you are looking for