In sales quotation document number not changed..

hiii guys
i getting some problem in sales quotation about document number.....
actually i opened by another user like sham.he is sales department..he have only sales authorizations..when we press add button, data has been saved..but number not changed... but after saving,we close form and open again then that that time number automatically changed..its comes serial number..when we press add button,,we getting same problem...

hi
I think you got confused with document and draft no on Approval documents.
Ofcourse many user,got this confusion.
The Document number wont be generated in Sales Quotation till you add it(i.e when waiting for approval)
The document number which is shown in that document when pending for the approval, is not the finalised number.
Its just the next number of sales quotaion which wont get stored in sales quotation,rather it will store in Draft table ODRF.
when you have too many documents which is waiting for approval,you can notice that document number will be same for all the other documents.
So you note down the Draft Number which is UNIQUE.
For Ex:
you are creating sales quotation which has the document number as '335'.
so when you sending it for approval the draft number will be staored as '211'.
after getting the approval,when you add it,document number will be generated as '337' because two documents were posted when the draft no:211 is waiting for approval.
revert me for any clarification.
Edited by: kambadasan on Feb 23, 2012 1:41 PM

Similar Messages

Sales document was not changed BAPI

Hi Experts,
        Am trying to upload sales documents using BAPI_SALESDOCU_CREATEFROMDATA1, but am getting an error like "sales document was not changed". here is my sample code. Thanks in Advance.
TYPE-POOLS : TRUXS.
types : BEGIN OF TY_file,
auart TYPE auart,
vkorg TYPE vkorg , "
vtweg TYPE vtweg ,
spart TYPE spart ,
KUNNR TYPE kunnr ,
KUNNR1 TYPE kunnr ,
matnr TYPE matnr ,
dzmeng TYPE dzmeng ,
WERKS_d TYPE werks_d ,
END OF TY_file.
*TYPES : tt_file TYPE STANDARD TABLE OF ty_file.
data : it_file TYPE TABLE OF TY_FILE,
               wa_file TYPE TY_file.
PARAMETERs : p_file TYPE IBIPPARMS-PATH.
at SELECTION-SCREEN on VALUE-REQUEST FOR p_file.
   PERFORM browse_file.
   START-OF-SELECTION.
   PERFORM LOAD_FLAT_FILE.
   PERFORM CALL_BAPI_CREATE.
FORM browse_file .
CALL FUNCTION 'F4_FILENAME'
IMPORTING
    FILE_NAME           = p_file
ENDFORM.                    " browse_file
FORM LOAD_FLAT_FILE .
   DATA : LT_RAW TYPE TRUXS_T_TEXT_DATA.
   CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
     EXPORTING
       I_FIELD_SEPERATOR          = 'X'
      I_LINE_HEADER              = 'X'
       I_TAB_RAW_DATA             = LT_RAW
       I_FILENAME                 = P_FILE
     TABLES
       I_TAB_CONVERTED_DATA       = IT_FILE
    EXCEPTIONS
      CONVERSION_FAILED          = 1
      OTHERS                     = 2
   IF SY-SUBRC = 0.
     MESSAGE 'UPLOADED' TYPE 'I'.
       ENDIF.
ENDFORM.                    " LOAD_FLAT_FILE
FORM CALL_BAPI_CREATE .
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                          WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                          WITH HEADER LINE.
LOOP AT IT_FILE INTO WA_FILE.
   header-doc_type = WA_FILE-auart.
   headerx-doc_type = 'X'.
   header-sales_org = WA_FILE-vkorg.
   headerx-sales_org = 'X'.
   header-distr_chan = WA_FILE-vtweg.
   headerx-distr_chan = 'X'.
   header-division = WA_FILE-spart.
   headerx-division = 'X'.
   headerx-updateflag = 'I'.             " flag for create a new document
   partner-partn_role = 'AG'.
   partner-partn_numb = WA_fILE-KUNNR.
   APPEND partner.
   partner-partn_role = 'WE'.
   partner-partn_numb = WA_fILE-KUNNR1.
   APPEND partner.
   itemx-updateflag = ''.
   item-itm_number = '000010'.
   itemx-itm_number = 'X'.
   item-material = WA_FILE-matnr.
   itemx-material = 'X'.
   item-plant    = WA_FILE-WERKS_d.
   itemx-plant   = 'X'.
   item-target_qty = WA_fILE-dzmeng.
   itemx-target_qty = 'X'.
   APPEND item.
   APPEND itemx.
   lt_schedules_in-itm_number = '000010'.
   lt_schedules_in-sched_line = '0001'.
   lt_schedules_in-req_qty    = WA_FILE-DZmeng.
   APPEND lt_schedules_in.
   lt_schedules_inx-itm_number = '000010'.
   lt_schedules_inx-sched_line = '0001'.
   lt_schedules_inx-updateflag = 'X'.
   lt_schedules_inx-req_qty     = 'X'.
   APPEND lt_schedules_inx.
   CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
        EXPORTING
             sales_header_in     = header
             sales_header_inx    = headerx
        IMPORTING
             salesdocument_ex    = v_vbeln
        TABLES
             return              = return
             sales_items_in      = item
             sales_items_inx     = itemx
             sales_schedules_in = lt_schedules_in
             sales_schedules_inx = lt_schedules_inx
             sales_partners      = partner.
* LOOP AT return WHERE type = 'E' OR type = 'A'.
*    EXIT.
WRITE : / RETURN-NUMBER, RETURN-TYPE, RETURN-MESSAGE.
* ENDLOOP.
* IF sy-subrc = 0.
*    WRITE: / 'Error in creating document'.
* ELSE.
*    COMMIT WORK AND WAIT.
*    WRITE: / 'Document ', v_vbeln, ' created'.
* ENDIF.
* LOOP AT RETURN.
*WRITE : / RETURN-NUMBER, RETURN-TYPE, RETURN-MESSAGE.
   ENDLOOP.
   END

Hi Experts,
        Am trying to upload sales documents using BAPI_SALESDOCU_CREATEFROMDATA1, but am getting an error like "sales document was not changed". here is my sample code. Thanks in Advance.
TYPE-POOLS : TRUXS.
types : BEGIN OF TY_file,
auart TYPE auart,
vkorg TYPE vkorg , "
vtweg TYPE vtweg ,
spart TYPE spart ,
KUNNR TYPE kunnr ,
KUNNR1 TYPE kunnr ,
matnr TYPE matnr ,
dzmeng TYPE dzmeng ,
WERKS_d TYPE werks_d ,
END OF TY_file.
*TYPES : tt_file TYPE STANDARD TABLE OF ty_file.
data : it_file TYPE TABLE OF TY_FILE,
               wa_file TYPE TY_file.
PARAMETERs : p_file TYPE IBIPPARMS-PATH.
at SELECTION-SCREEN on VALUE-REQUEST FOR p_file.
   PERFORM browse_file.
   START-OF-SELECTION.
   PERFORM LOAD_FLAT_FILE.
   PERFORM CALL_BAPI_CREATE.
FORM browse_file .
CALL FUNCTION 'F4_FILENAME'
IMPORTING
    FILE_NAME           = p_file
ENDFORM.                    " browse_file
FORM LOAD_FLAT_FILE .
   DATA : LT_RAW TYPE TRUXS_T_TEXT_DATA.
   CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
     EXPORTING
       I_FIELD_SEPERATOR          = 'X'
      I_LINE_HEADER              = 'X'
       I_TAB_RAW_DATA             = LT_RAW
       I_FILENAME                 = P_FILE
     TABLES
       I_TAB_CONVERTED_DATA       = IT_FILE
    EXCEPTIONS
      CONVERSION_FAILED          = 1
      OTHERS                     = 2
   IF SY-SUBRC = 0.
     MESSAGE 'UPLOADED' TYPE 'I'.
       ENDIF.
ENDFORM.                    " LOAD_FLAT_FILE
FORM CALL_BAPI_CREATE .
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                          WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                          WITH HEADER LINE.
LOOP AT IT_FILE INTO WA_FILE.
   header-doc_type = WA_FILE-auart.
   headerx-doc_type = 'X'.
   header-sales_org = WA_FILE-vkorg.
   headerx-sales_org = 'X'.
   header-distr_chan = WA_FILE-vtweg.
   headerx-distr_chan = 'X'.
   header-division = WA_FILE-spart.
   headerx-division = 'X'.
   headerx-updateflag = 'I'.             " flag for create a new document
   partner-partn_role = 'AG'.
   partner-partn_numb = WA_fILE-KUNNR.
   APPEND partner.
   partner-partn_role = 'WE'.
   partner-partn_numb = WA_fILE-KUNNR1.
   APPEND partner.
   itemx-updateflag = ''.
   item-itm_number = '000010'.
   itemx-itm_number = 'X'.
   item-material = WA_FILE-matnr.
   itemx-material = 'X'.
   item-plant    = WA_FILE-WERKS_d.
   itemx-plant   = 'X'.
   item-target_qty = WA_fILE-dzmeng.
   itemx-target_qty = 'X'.
   APPEND item.
   APPEND itemx.
   lt_schedules_in-itm_number = '000010'.
   lt_schedules_in-sched_line = '0001'.
   lt_schedules_in-req_qty    = WA_FILE-DZmeng.
   APPEND lt_schedules_in.
   lt_schedules_inx-itm_number = '000010'.
   lt_schedules_inx-sched_line = '0001'.
   lt_schedules_inx-updateflag = 'X'.
   lt_schedules_inx-req_qty     = 'X'.
   APPEND lt_schedules_inx.
   CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
        EXPORTING
             sales_header_in     = header
             sales_header_inx    = headerx
        IMPORTING
             salesdocument_ex    = v_vbeln
        TABLES
             return              = return
             sales_items_in      = item
             sales_items_inx     = itemx
             sales_schedules_in = lt_schedules_in
             sales_schedules_inx = lt_schedules_inx
             sales_partners      = partner.
* LOOP AT return WHERE type = 'E' OR type = 'A'.
*    EXIT.
WRITE : / RETURN-NUMBER, RETURN-TYPE, RETURN-MESSAGE.
* ENDLOOP.
* IF sy-subrc = 0.
*    WRITE: / 'Error in creating document'.
* ELSE.
*    COMMIT WORK AND WAIT.
*    WRITE: / 'Document ', v_vbeln, ' created'.
* ENDIF.
* LOOP AT RETURN.
*WRITE : / RETURN-NUMBER, RETURN-TYPE, RETURN-MESSAGE.
   ENDLOOP.
   END

Invoice number and document number not printed in payment advice

Hello Gurus,
I am executing reprint check through transaction fch7, In that Invoice number and document number not printed in payment advice. I have created zscript for that and also assinged regup-belnr and regup-xblnr and used standard program RFFOUS_C.
other fields from regup table are displayed but above two mentioned fields are not displayed.
I even tried debugging standard RFFOUS_C prog, in that regup-belnr and regup-xblnr are coming but it is not printed on form.
With regards,
Vikram

Hi,
Debug you Zscript and check the invoice no and document no. Have assigned that script in FBZP..? check the which form is calling FCH7 in debugger mode..?
Rgds
Aeda.

Customer document number not picked while making payment

Hi guys
we have one vendor the same vendor as customer also. while we making payment to vendor customer document document number not picked,, the erro message comes.. " NO APPROPRIATE LINE ITEM IS CONTAINED IN THE DOCUMENT"
But we already assigned the following:-
1) In Vendor master data, Customer code has been given
2) In Documnet type KZ, we select vendor also.
But still the customer document not picked while making payment
Pl Help me out.
Regards
K.Gururajan

Hi,
Check the following:
1. The check box clearing with customer and clearing with vendor has been selected in both the masters in the payment transactions tab.
2. Ensure the vendor is not locked up in any payment proposal in F110.
Thanks
Aravind

Arbitrary Number Generated before Sales Order Document number is Generated

I want to know which is the arbitrary number generated before the sales Order Document number is created. In which table the arbitrary number is stored?
The Exit which triggers the arbitrary number in the transaction VA01?

Hi
You get the Arbitrary number throug the FM NUMBER_GET_NEXT.
interne Nummernvergabe
        data: da_rc like inri-returncode.
        call function 'NUMBER_GET_NEXT'
          exporting
            nr_range_nr = da_numki
            object      = 'RV_BELEG'
          importing
            returncode = da_rc
            number      = vbak-vbeln.
And regarding userexit, there is
perform userexit_number_range using da_numki statement in include MV45AF0B_BELEG_SICHERN.
Regards
Raj

Excise invoice Internal document number not populating.

Expert,
In STO supplying plant Movt-351 document posted , J1IS EXcise invoice has done ,here while saving the Excise invoice Internal document number not populating.
But number ranges (J_1iexcloc ) is done correctly against the year.
Logistics->Tax on Goods Movements->India->Tools->Number Ranges.
This is urgent Tickets ,can anyone help me out ?
regards,
kumar

Dear prasanna ,
Official excise document number in quality server is populating perfectly,where as prod server not populating , in quality server object is J_1IEXCLOC ,same object assigned to prod server . i did not assgined J_1IINTNUM object in Quality server.
why its not populating ?
thanks
kumar

Sales document number not updated in FI document

Hi,
Whenever invoice creates in FI through billing document, system will not update sales document number in FI document(Invoice). Please confirm if there is any way to update sales document number in FI document because I want to create dunning notices on sales order basis.
Request immediate help.
Thanks in advance.

Hi,
In the standard system, FI postings will be updated with FI document numbers only. If you want to see respective billing document number in customer ledger, go to FBL5N, select 'Change Layout' icon and move billing document number from 'hidden fields' to display fields list and see.
Regds
Sarma BH

Sales document number not appearing in Work Item.

Hello gurus,
     I have created a WorkFlow for approval of Sales order. My problem is, the sales document number is not appearing in the WorkItem for user decision task. I am passing container variable the sales document number in the Parameter1 of the User Decision task of the work flow. Value is populated correctly in the container variable for sales document number, but fails to appear in the work item content in SBWP.
     Please suggest a solution.
Regards,
Dnyanesh.

Hello All,
     Thanks for your reply.
I am passing the value of sales document number in parameter 1 of the standard task for approval as below.
But in my Business Workplace I do not get the Sales document number. Below is the screenshot.
Regards,
Dnyanesh.

Invoice/billing document Number not appearing on sales order document flow

Dear all,
After saving the sales order invoice when i check in va02 sales order document flow invoice number is not generating

Really something is wrong in your configuration. When your delivery status shows Being Processed, I could see subsequent two documents, viz.Confirmation of Service and GD doc reference as complete.
Can you let me know how many line items that delivery contains? The reason for this query is normally, for stock item, we see Material Document reference and for non-stock item, we see Confirmation of service. But in your case, I could see both. From your VBFA table screen shot, I could see two different material document references.
G. Lakshmipathi

In the Production Order, Sales Quotation is displayed not the Sales Order

Hello to All,
I need a kind help from you.
My scenario is as follows
There is a Configurable Material (Finished Product)
Sales quotation (VA21/2/3) were made for this material.
Sales Order (VA01/2/3) with reference from the Sales Quotation were made for this same material.
Now when I run the MRP (MD02) for this material, Planned Orders were created.
Planned orders were converted to the Production Order.
In the Production Order (say in Display mode), under the 'General' tab, there is a segment called 'Sales order'. In this segment, the sales order is being displayed if the Production Order is created for a sales order (MTO scenario).
But, in my case, the Sales Quotation number is being displayed instead of the Sales order.
My Issue which need your answers:
Is it a standard SAP scenario?? I mean, if the production order is created for a sales order and again if the sales order is created earlier with reference to a sales quotation, then in the production order, the Sales quotation is displayed. Is it a standard?? Or it is showing wrongly? I mean, is it like that, always the sales order should be displayed in the Production order and not the sales quotation??
Please suggest so that I can overcome this problem, if at all it is a problem.
Some More Inputs (For your analysis/research):
1. After the MRP run of the material the Planned Order is created. I have checked the planned order, and found tha the assignment of sales document (in this case Quotation) is done in the Planned order itslef. It is visible wthin the "Assigmnet" tab of the Planned Order.
2. For the analysis purpose, I created one stand-alone Sales Order for the same material. I mean, without reference from any Sales Quotation. Then, when I run the MRP (md02), the Planned Order and then production order were created normally, with reference to the Sales order. This just for your kind information.
3. I have checked the pegged requirement of the Production order in the MD04. It is showing the Sales order itself. But, if I see the production order (CO02/O03), it shows sales quotation.
User Requirement:
Evenif, the sales order is created with reference to a Sales Quotation, after MRP run, in the Planned and thereby subsequent production order, the Sales Order should display and not the Sales quotation.
Please suggest.
Thanks and Regards,
Supriyo

Hi
Since your scenario is configurable material, the system takes the reference of sales quotation only. Because the in case of configurable materials the sales quotation is the base and based on the sales quotation the sales order is created and subsequent production order.
This is std SAP and for configurable materials the sales quotation is deciding factor
Krishna

Document number not within defined interval

I am trying to assign my own po number with idoc pordcr101
i am using the next po in our system 4500016058.
when i look in we02 after sending the idoc i see
document 4500016058 not within defined interval.
can i assign my own po? do i need to define my interval somewhere?
any help would be greatly appreciated.
thank you

Hi Janice,
You are trying to create a PO with your specified Number, but in R/3 document numbers can exist only in the interval specified, hence check the number range in your R/3 config. and accordingly pad your number with 0's.
Or you will have to change the interval ( Basis Job ).
P.S. Also check if your R/3 allows External Number generation.
Regards.

Document Number not being updated

Hello
I am running into this issue at the time of posting any FI document (invoice/payment/reversal). I get an error saying ex: Doc #1900000000 already exists. which is true, that document already exists. the problem is that it is the first number in the range. I have already posted more than 50 documents and the next number should be 19000000051 or something. I checked the number range and none of them are assigned externally. I also noticed that the current status for all was "0" instead of the current number. So i manually updated the current number and was able to post that document. However, the current document number in FBN1 (Status) did not get updated so I was not able to post the next consecutive document and get the same error (saying document 190000051 already exists). Its like the system is not automatically picking the next consecutive number.
I am not sure what the issue is because i didnt have any problems until yesterday. Could it be due to the period change (Sept 1st today)
Any help would be highly appreciated
thanks
Nubha

Hi Nubha,
Can you please re-check in tables Number ranges for Document type, same Number range you have assigned the Number range Intervals.
Check Table T003 for Document type to Number range
Check Table TNRGT for Number range for intervals
Thank you
Anil

Argentina official document number range (Changing of XBLNR)

Hi All,
Working on a typical requirement.
As some of you are aware, the official document number (XBLNR) is getting generated by system based on branch, document type, document class and print character.
Is there any posibility to change this value before the Accounting document is going to be created(after I press save)?
Is there any userexits/BADIs/BTEs that will trigger before this official document number is going to be generated, so that I can change XBLNR value?
Does anybody had encounter such situation? if so please let me know.
Appreciate your help on this.
Regards,
Nanda.

Please check below function modules (J_1A_OFF_NUMBER_GET, EXIT_SAPLV60B_001)and user exits. In following function module the official document number is generated. Normally you do not change this.
Function module: J_1A_OFF_NUMBER_GET
Text
Official document numbering in Argentina
Functionality
This function module determines an Argentine official document number, it is using the input values to determine a numbering subobject for the numbering object J_1AOFFDOC and calls the numbering module NUMBER_GET_NEXT for this object and number range '01'.
Parameters
I_BUKRS
I_SNR
I_PRTCHR
I_DOCCLS
I_DATE
E_DOCNR
E_DATE
E_DATE_ERROR
E_XBLNR
Exceptions
CLASS_NOT_DEFINED
INPUT_NOT_VALID
PRTCHR_NOT_FILLED
DETERM_NOT_POSSIBLE
ERROR_NUMBER_GET
Function Group
J1AN
J_1A_OFF_NUMBERING
J_1AFONR
Short text
Printing of the last official documents numbers assigned
Description
List the last used official document numbers in the sytem for every combination of document class, branch and printing character who are self-issued (relevant for numbering) -for a certain period-
Requirements
Assignation of number ranges and numbering groups for self-issued document types
The period of time where the report looks for the documents have an initial and a final date in the screen:
u2022     The final date is obligatory field, because is the searching limit.
u2022     The initial date field it is not obligatory.
o     When it is not filled, the report looks for the documents in all the historical data until the final date, this can be high-time-consumer.
o     When the first date is filled the report looks in the interval of time -recommended-.
The resulting list present considerable changes depending on the date intenval definition
Output
The first list contains the following fields:
u2022     Reference fields: describe where the document come from (document type FI, Delivery and Billing Type SD, Material Movement MM)
u2022     KeyFields: Document Class, Branch and Printing Character.
u2022     Result: Last official number or a legend when no document is found.
The option for to make a variant of the list is available
By the button SummaryLIST is possible to access a second list with the result information by the unique possible combinations of the KeyFields (Making omission of the reference fields)
Access to a document: by clicking in the official number.
Function module J_1A_OFF_NUMBER_CHECK
No doc available
'OFF_NUMBER_GLOBAL_NUMBERING'
CALL FUNCTION 'OFF_NUMBER_GLOBAL_CHECK'
    EXPORTING
      i_fin1_param = fin1_param
      i_bkpf       = bkpf
    EXCEPTIONS
      OTHERS       = 0.
Display/change official document numbers: transaction J1A6
Next to substitution (tx OBBH) you can use Program LXVVFU01 User Exit AC Interface (Header Line).
function module EXIT_SAPLV60B_001:
FUNCTION EXIT_SAPLV60B_001.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(XACCHD) LIKE ACCHD STRUCTURE ACCHD
*"     VALUE(VBRK) LIKE VBRK STRUCTURE VBRK
*"     VALUE(XACCIT) LIKE ACCIT STRUCTURE ACCIT
*"     REFERENCE(DOC_NUMBER) LIKE VBRK-VBELN OPTIONAL
*" EXPORTING
*"     VALUE(XACCHD) LIKE ACCHD STRUCTURE ACCHD
*"     VALUE(XACCIT) LIKE ACCIT STRUCTURE ACCIT
*" TABLES
*"      CVBRP STRUCTURE VBRPVB OPTIONAL
*"      CKOMV STRUCTURE KOMV
INCLUDE ZXVVFU01.
ENDFUNCTION.
Include/ userexit ZXVVFU01 (sample code):
*for Argentinean legal document numbering the field xblnr should be used for the legal document *number.
if vbrk-vkorg = 'ARXX'.
    case vbrk-fkart.
      when 'F2 '.
*factura
        XACCIT-BLART = 'RV'.
*nota de credita
      when 'GAE '.
      XACCIT-BLART = 'DG'.
      when 'ZGAE'.
      XACCIT-BLART = 'DG'.
                     retorno
      when 'ZR70'.
      XACCIT-BLART = 'DG'.
*nota de debito
      when 'ZLAE'.
        XACCIT-BLART = 'RV'.
      when 'LAE '.
        XACCIT-BLART = 'RV'.
      when others.
    endcase.
    xaccit-xblnr = xaccit-xblnr+0(16)
endif.
Via customizing (cross applications Cross-Application Components / General Application Functions / Cross-Application Document Numbering ´/ Argentina ) you can set up the document numbering.
Hope this helps!

Free item reference document number not populated in MIGO item screen

Hi
I have a requirement where in I would need to populate the reference document number in the MIGO item when I am cancelling a goods receipt in case of free items.
In standard SAP system we know that it would only be populated when GRbased IV is ticked in PO but in free item PO this is not ticked . So was enquiring if any body knows how we could populate the reference document number at GR cancellation in MIGO item level for free items .

Hi,
If you mean the field MSEG-SMBLN, then it is always populated at cancellation, no matter the GR-based IV flag.
BR
Raf

Document Number Not Generate In FEBA ( Bank Reconciliation)

Dear All,
We have configured all the required details for Manual Bank Statement for Bank Reconciliation .
Steps :
1 ) Take converted file from Bank
2 ) Upload that file in Text format into System then system automatically update FF67.
3) Go into FEBA , then we got cleared items but we are not able to get Accounting Document Number .
How we can get Accounting Document Number in FEBA ??
Regards,
Kaushal Shah

Hi,
Sorry, just today I checked your message.
Instead of processing BDC, you have to post through FEBA.
ie. Download the statement with the option Do not post or post online.
Then process the error lines or all documents through FEBA. Then you can able to see the document number.
If the posting is done at the background through batch jobs, then there will not be any document number visible through FEBA.
Let me know if you need any more information.
Regards,
Prabha

In sales quotation document number not changed..

Similar Messages

Maybe you are looking for