Baseline date not flowing in MIRO transaction

Hi
Baseline date not flowing in MIRO while doing transaction.
We have maintained Payment terms in vendor master record
and payment terms maintained in PO also.
We have done the GR posting.
please help
Thanks and regards
Aakash

Are you use an MIRO with amount split? and does your payment term is configured with "No Default Date'? Then refer to OSS 495303.

Similar Messages

Baseline date not default in MIRO for Invoices posted against STO Pu.Order

Hi All,
Baseline date doesn´t default in MIRO for Invoices posted against an STO Purchase Order.
We are trying to post an Invoice in MIRO with reference to a STO Purchase Order for planning delivery cost.
Delivery cost in PO has not got the Vendor number because conditions are customized not possible to process manually so in MIRO the system asks to enter the Invoicing Party and then the baseline date.
The client requires that when the invoicing party is enter manually in MIRO, the term of payment should be pick up from Vendor Master Record.
Could someone confirm if this possible ?
Thanks and regards,
Laura

Hi Laura ,
The payment terms in Invoice are taken from PO only .
Refer SAP Note : 177224 for more details.
Regards
Ramesh Ch

ADC for Domestic Purchase not flowing in MIRO for particular MIGO Document

Hello Experts,
    We've a scenario in which we pay ADC to domestic vendor. The procedure we follow is as below:
          1. Condition record for JAOP with 0% rate maintained in FV12.
          2. PO created with JMOP 10%, 2% ECS, 1% SECS & 4% VAT.
          3. During MIGO (also excise invoice capture), AED value is maintained
          4. After J1IEX, at the time of MIRO this ADC along with other duties flows in simulation
    Now in my case, there are number of GR documents for which MIRO is performed, but for particular GR, ADC is not flowing in MIRO and also excise duty is incorrect, it's not flowing from GR.
   So what is the probable solution for this, I've already checked MIGO & excise invoice documents & found to be ok.
Thanks in advance
        Amit

Hi,
Have you maintained material price including AED price??
If yes then check whether you have maintained JAX1-100% or not?
I think this should be treated as a dealer purchase as you are maintaining 0% amount for JAOP.
Regards,
Piyush

Correct values not flowing in MIRO when values are changed in J1IEX

D/ Friends,
In Purchase Scenario with mov typ 101, when we capture excise duty thru T.Code J1IEX, sometimes we need to change the Duty Rates as well as Excise base Value (i.e.***. Value). We change these 2 things & we also change the BED, ECess & SH Cess values manually. Thereafter we do GRN & then post the EI.
Now the issue is that when we do MIRO, the duties Posted in EI in J1IEX, are not flowing in MIRO. Pls note that such scenario is occurring only when we change the above 2 things in J1IEX. Pls advice.
Rgds.

pl check excise defalt for your tax procedure JCV1 condition assigned or not.
regards
karthik

Entering the text in note tab in MIRO transaction

hai friends,
can u please tell how to store a text in note tab in MIRO transaction usging function module.
please help me.
Regards,
N.selvamuthukumar

Hi
I need to program the same. Can you please send the details of how you implemented it.

Baseline Date not chaning using BADI FAGL_SET_SEGMENT

If someone has worked with this badi FAGL_SET_SEGMENT, can you please help.
I'm trying to change the baseline date for the vendor invoice created using FB60. I implemented the above BADI and changed the value of Baseline Date and Cash discount days based on the business logic. But the change is not reflecting in the document.
Please help.
Thank you.

I understand the proposed solution but I do not think this should be a custom coding requirement. The underlying assumption of the invoice payment term is that goods / services have been delivered. The transfer of title should be a configurable trigger for the vendor payment baseline date. Many consumer goods are shipped FOB to the customer destination with a 3-4 week shipping timeline. Normal payment terms run 30-45 days. We want our baseline date to start when the title transfers. I can understand the GR document does not take the place of a proof of delivery but it is much closer to the the point where we actually transfer title then when we normally receive the invoice (2 days after vendor shipment). Of course I have been through the argument that the invoice document date should be manipulated but I do not buy into it because it envokes a form of dispute management on a standard flow. Initially I went down the path of GR based IV which follows the same logic as above for the release of ultimate payment. I am confused as to why the standard solution does not provide an equivalent configuration for baseline date computation. Can anyone explain why this is the case or whether I am just missing something obvious?

PO Conditions not flowing in MIRO

Hi,
This is a case of Import Purchasing where Invoice Verification (for Custom/CVD) is done before goods receipt.
It is observed that in the screen MIRO the condition values (for duties of Custom/CVD) are not flowing from PO although values are maintained in PO. Amount and quantity need to be entered manually in MIRO in this case.
Is this a standard behaviour of SAP that if IV is done before GR then condition value doesn't flow from PO and need to be entered manually in MIRO? And is there any way out / work around in order to get the condition values flown from PO to MIRO if IV is done before GR?
Can any one assist in getting this query resolved?
Thanks in advance

yes, this is the standard behaviour. In import procurement we need to enter manually the value of conditions.
No, there is no any customization through which we can get the flow of value automatically.
But, u can drag the value and qty of conditions---
when u will do IV against the layout of PLANNED DELIVERY COST, there u will find the right side two columns Recieved QTy and Value. from that columns, u can drag the value and qty.
thanks

Baseline date not as default setting

HI all,
payment term Z000 has default baseline date as posting date.
upon entry, doc date = 01.01.2006, posting date = 31.01.2006 BUT baseline date picks up 01.01.2006.
what other setting did the system checks?
thanks.

Hi
in customising for terms of payment you must set for default for baseline date
the posting date and
not the document date
this is the reason for the problem
BR Tarik

Baseline date not driving the due date

My client is currently implementing ECC 6.
In my past project, I had always thought that the baseline date drives the due date of a vendor invoice for example. But in transaction FB60, when i put in my baseline date, the due date gets calcualted using the payment terms. Is this correct? My client would like the baseline date to drive the due date for paying invoices. How can I correct this please?
Thanks for your help.

Hi,
Yes, it is possible to overwrite the baseline date while making the posting in FB60. However, the payment terms is also taken into account for calculating due date. For example if payment terms id P30 - net due 30 days, the due date will be 30 days from baseline date.
If baseline date is May 29th 2007, due date will be Jun 27th 2007
If baseline date is changed to May 31st 2007, due date will change to Jun 30th 2007.
Probably, you would like to increase or decrease the credit period days, which can done by changing the payment terms.
Thanks
Murali.

Item line data not flowing into SAP Adobe form layout

Hello Gurus,
I am currently working on adobe form layout for a sales document in SAP, i have created a master page
as well as a couple of pages in the design view. Data at the header level are working properly, but the item data
are not flowing into the layout, as nothing appears in the print preview for the item level of the sales document.
I have done all the necessary binding with all the right field names, my subform to the best of my knowledge seems to be well
defined, but yet to no avail.
I would like to know what yet could be the reason for this issue and how i can go about fixing it.
Thank you.
Ahm.

Hi Vijai,
In our project, we have the same requirement but I am one step behind than you. I am able to generate the PDF form but not able to generate the data. Means all the fields are coming as disabled fields.
Can you please send your code as a sample code so that I can have a look at that and check where I am doing wrong/missing. My id is sandeep.kamdar in gmail
Thanks & Regards,
Sandip Kamdar

Baseline date not getting populated from SRM invoices posted to ECC 6.0

Hi,
We are currently in ECC 6.0. The SRM system is in 4.0. We have this particular problem that the baseline date is not getting populated from the Invoices posted from the SRM. The baseline date is blank and the document is saved.
Did anyone face the same problem??? Can you please refer SAP note 541934 and expand........
Thanks
Aravind
Edited by: Aitipamula Aravind on Aug 10, 2009 5:13 AM

Hello,
Yes, you could check the attached note 541934 and regard the implementation of the field ZFBDT in the invoicing document.
Note 541934 provides a solution how to achieve the MM-customizing for payment baseline dates getting effective for invoices with SRM-origin. This note needs to be applied at your ERP-MM-side in the former plug-in-layer. As described in the note, this is a modification. It's recommended to apply in non-productive system first.
Hope the above infor.are helps for you!
Best Regards,
Gladys xing

Sales employee related data not flowing in standard report MCTI and VF05

Dear All
I have created a partner function sales employee by coping VE.All assignments in partner determination done.After maintaining sales employee in customer master it is flowing to sales order.After processing invoice when i check the standard report MCTI and in VF05 under partner function tab,.the data is not flowing.I checked in the OVRP setting are there.
Please guide.
Regards,
Deepti

Hi,
Are you updated it as daily in OMO1
double click on infostructure S006 and select daily and see
Kapil

Help needed-Survey template data not flowing from CRM to Mobile & V V

Hi experts,
We have a requirement to create a custom survey template and pass it to mobile. The data flow should be to and fro. as in; from CRM to Mobile Application and vice versa.
Currently we are facing an issue in this that the data if not being passed properly from the CRM TO Moblie.
As i am new to the middleware concepts, i am not sure how to go about analysing if my data in the BDocs for the survey template if correct or not.Some data is present for the survey in the Bdoc(xml), but i am not sure if this xml value is correct or not as the Bdoc table entry (xml value)seems to have been truncated(i cannot view the entire xml there wen i try to open the BDoc fields in SMW01).
any pointers to this is highly appreciated.
Thanks
Swapna.

May be this thread will help
v('APP_USER') not returning HTMLDB user
regards,
Shijesh

Bdc Screen data not passing to XK01 transaction screen for the second PO

Hi Friends,
                I have an requirement to extend an existing vendor to multiple company code and for multiple purchase organisation.I have created one report that will list the company code and the purchase organisation to be extended for the vendor. I am calling the standard program as below.
          LOOP AT li_porg.
          If user has ALSO selected p. organizations to extend...
            IF NOT li_company[] IS INITIAL.
              LOOP AT li_company.
                SUBMIT zricef666 WITH ld_par = ld_param
                                 WITH ls_vend = ls_vendor_ampl
                                 WITH ld_bukrs = li_company-bukrs
                                 WITH ld_ekorg = li_porg-ekorg
                         AND RETURN.
              ENDLOOP.
          ENDLOOP.
Within the program zricef666 , i am calling the below program to extend vendor.
SUBMIT RFBIKR00 WITH ds_name = FICH
               WITH xlog = ld_mark
                AND RETURN.
Now the problem i am facing is that the first vendor got extended sucessfully for the first PO.But for the second PO , the screen fields are blank and it stuckes in that screen. But in the session i am able to clearly see the data are there but these data are not passing to the screen of XK01.
    Need help to solve this problem from you all.Thanks in advance.
With Regards,
Ajit Prasad.

Hello Ajit, try with the following code and reward if useful. the following code uses the transaction XK01.
REPORT zbdcxk01 .
DATA: BEGIN OF itab OCCURS 0,
        lifnr LIKE rf02k-lifnr,
        bukrs LIKE rf02k-bukrs,
        ktokk LIKE rf02k-ktokk,
        name1 LIKE lfa1-name1,
        sortl LIKE lfa1-sortl,
        land1 LIKE lfa1-land1,
        brsch LIKE lfa1-brsch,
        akont LIKE lfb1-akont,
        zterm LIKE lfb1-zterm,
        reprf LIKE lfb1-reprf,
        zwels LIKE lfb1-zwels,
      END OF itab.
DATA: rc TYPE i,
      flag TYPE i VALUE 1,
      it_files TYPE filetable,
      bdc_data TYPE STANDARD TABLE OF bdcdata WITH HEADER LINE.
DATA:   messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-002.
PARAMETERS: p_file(1024) TYPE c OBLIGATORY.
PARAMETERS:dismode DEFAULT 'A',
           updmode DEFAULT 'S'.
SELECTION-SCREEN : END OF BLOCK b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL METHOD cl_gui_frontend_services=>file_open_dialog
CHANGING
     file_table              = it_files
     rc                      = rc.
*Read the Filename into P_FILE
READ TABLE it_files INDEX 1 INTO p_file.
START-OF-SELECTION.
PERFORM getdata.
PERFORM create_session.
LOOP AT itab.
    PERFORM fill_bdc_table.
ENDLOOP.
PERFORM close_session.
END-OF-SELECTION.
PERFORM submit.
*&      Form getdata
*       text
FORM getdata.
DATA: file TYPE string.
file = p_file.
CALL FUNCTION 'GUI_UPLOAD'
       EXPORTING
            filename                = file
            has_field_separator     = 'X'
       TABLES
            data_tab                = itab
       EXCEPTIONS
            file_open_error         = 1
            file_read_error         = 2
            no_batch                = 3
            gui_refuse_filetransfer = 4
            invalid_type            = 5
            no_authority            = 6
            unknown_error           = 7
            bad_data_format         = 8
            header_not_allowed      = 9
            separator_not_allowed   = 10
            header_too_long         = 11
            unknown_dp_error        = 12
            access_denied           = 13
            dp_out_of_memory        = 14
            disk_full               = 15
            dp_timeout              = 16
            OTHERS                  = 17.
*IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
*ENDIF.
ENDFORM.                    " getdata
*&      Form CREATE_SESSION
*       text
FORM create_session.
CALL FUNCTION 'BDC_OPEN_GROUP'
   EXPORTING
     client                    = sy-mandt
*   DEST                      = FILLER8
     group                     = 'MYGROUP'
*   HOLDDATE                  = FILLER8
     keep                      = 'X'
     user                      = sy-uname
*   RECORD                    = FILLER1
* IMPORTING
*   QID                       =
   EXCEPTIONS
     client_invalid            = 1
     destination_invalid       = 2
     group_invalid             = 3
     group_is_locked           = 4
     holddate_invalid          = 5
     internal_error            = 6
     queue_error               = 7
     running                   = 8
     system_lock_error         = 9
     user_invalid              = 10
     OTHERS                    = 11
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " CREATE_SESSION
*&      Form CLOSE_SESSION
FORM close_session.
CALL FUNCTION 'BDC_CLOSE_GROUP'
       EXCEPTIONS
            not_open    = 1
            queue_error = 2
            OTHERS      = 3.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " CLOSE_SESSION
*&      Form FILL_BDC_TABLE
*       text
* --> p1        text
* <-- p2        text
FORM fill_bdc_table.
REFRESH bdc_data.
PERFORM operation.
CALL FUNCTION 'BDC_INSERT'
   EXPORTING
     tcode                  = 'XK01'
*   POST_LOCAL             = NOVBLOCAL
*   PRINTING               = NOPRINT
    TABLES
      dynprotab              = bdc_data
* EXCEPTIONS
*   INTERNAL_ERROR         = 1
*   NOT_OPEN               = 2
*   QUEUE_ERROR            = 3
*   TCODE_INVALID          = 4
*   PRINTING_INVALID       = 5
*   POSTING_INVALID        = 6
*   OTHERS                 = 7
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
PERFORM bdc_transaction USING 'XK01'.
ENDFORM.                    " FILL_BDC_TABLE
*&      Form BDC_DYNPRO
*       texT
* --> p1        text
* <-- p2        text
FORM bdc_dynpro USING program dynpro.
CLEAR bdc_data.
bdc_data-program = program.
bdc_data-dynpro = dynpro.
bdc_data-dynbegin = 'X'.
APPEND bdc_data.
ENDFORM.                    " BDC_DYNPRO
*&      Form BDC_FIELD
*       text
FORM bdc_field USING fnam fval.
CLEAR bdc_data.
bdc_data-fnam = fnam.
bdc_data-fval = fval.
APPEND bdc_data.
ENDFORM.                    " BDC_FIELD
*&      Form BDC_TRANSACTION
FORM bdc_transaction USING tcode.
CALL TRANSACTION tcode USING bdc_data
                         MODE   dismode
                         UPDATE updmode
                         MESSAGES INTO messtab.
ENDFORM.                    " BDC_TRANSACTION
*&      Form SUBMIT
*       text
FORM submit.
SUBMIT rsbdcsub EXPORTING LIST TO MEMORY AND RETURN
*                  user sy-uname
                    WITH mappe = 'MYGROUP'
                    WITH von   = sy-datum
                    WITH bis   = sy-datum
                    WITH z_verarb = 'X'.
ENDFORM.                    " SUBMIT
*&      Form OPERATION
*       text
FORM operation.
PERFORM bdc_dynpro      USING 'SAPMF02K' '0100'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'RF02K-KTOKK'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
PERFORM bdc_field       USING 'RF02K-LIFNR'
                                itab-lifnr.
PERFORM bdc_field       USING 'RF02K-BUKRS'
                                itab-bukrs.
PERFORM bdc_field       USING 'RF02K-KTOKK'
                                itab-ktokk.
PERFORM bdc_dynpro      USING 'SAPMF02K' '0110'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'LFA1-SORTL'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
PERFORM bdc_field       USING 'LFA1-NAME1'
                                itab-name1.
PERFORM bdc_field       USING 'LFA1-SORTL'
                                itab-sortl.
PERFORM bdc_field       USING 'LFA1-LAND1'
                                itab-land1.
PERFORM bdc_dynpro      USING 'SAPMF02K' '0120'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'LFA1-BRSCH'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
PERFORM bdc_field       USING 'LFA1-BRSCH'
                                itab-brsch.
PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'LFBK-BANKS(01)'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=ENTR'.
PERFORM bdc_dynpro      USING 'SAPMF02K' '0210'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'LFB1-AKONT'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
PERFORM bdc_field       USING 'LFB1-AKONT'
                                itab-akont.
PERFORM bdc_dynpro      USING 'SAPMF02K' '0215'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'LFB1-REPRF'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=UPDA'.
PERFORM bdc_field       USING 'LFB1-ZTERM'
                                itab-zterm.
PERFORM bdc_field       USING 'LFB1-REPRF'
                                itab-reprf.
PERFORM bdc_field       USING 'LFB1-ZWELS'
                                itab-zwels.
PERFORM bdc_transaction USING 'XK01'.
ENDFORM.                    " OPERATION

VAT should post based on PO date or GR date not based on MIRO posting date

Hi,
Based on posting date in Invoice(MIRO) & condition record validity period, VAT is calculated & posting on invoice posting.
Condition record for VAT condition type with tax code(T9):
01.01.2011 to 31.01.2011-------> 4%
01.02.2011 to 28.02.2011------->12%
01.03.2011 to 31.03.2011------->14.5%
PO created and GR done on February & invoive done on March and syatem calculated VAT amount perfactly based on validity period maintained in condition recod and invoice posted.
But requirement is system should post invoice VAT amount as mentioned in the PO ( based on PO date) or GR date to post during Invoice posting in MIRO
Regards,
Biju K

Hi,
Any other input?
Regards,
Biju K

Baseline date not flowing in MIRO transaction

Similar Messages

Maybe you are looking for