Error in financial document creation vx11n

Dear Gurus,
After entering details in general data tab, when i go to status tab page
Status screen: A document has been created- which should not gray out and allow me to click on Status A. if I click on A, the time of creation of document will flow there.
But in this case the screen is grayed. There by not allowing to go ahead. Please note that the document to be used in sales doc should have a status set as D.
thanks in advance
Regards
vamsi

Hi Santosh
No problems. You can still click "D" in the status tab so that the date will flow in this column. Now you can save it.
Thanks
G. Lakshmipathi

Similar Messages

REQUIREMENT TO STOP BALANCE SHEET ACCOUNTS FROM ACCEPTING PROJECT AT JOURNAL CREATION OR ANY FINANCIAL DOCUMENT CREATION.

Dear Gurus,
I have a requirement from my client to stop balance sheet account from accepting project at financial document creation or journal entry because this process distrupt the profit and loss account report or transaction report by project as balance sheet items are not expected to be part of this report.
Kindly advise on the way to achieve this to enable fulfill requirement and deliver excellence service.
Kind regards,

Hi Nagarajan,
Thank you for your response.
My sample is whenever an entry is raised to be posted to a balance sheet account such account should not allow user to post but only in revenue and expense account. E.g. A Stock account should not allow project assignment but a cost of sales, expenses or sales revenue accounts should only accept project assignment.
Only P&L items should allow project assignments.
I hope this is clear is enough.
Regards,

Error in financial document

When trying to change an Sales standard order for a material, system is showing a message that "Financial documents : No financial document assigned" . What is this message means ?
Moderator: Please, avoid asking basic questions

Hi,
Please refer to the below links which could be helpful to you:
Financial documents: No financial document assigned
http://help.sap.com/saphelp_45b/helpdata/en/93/744a58546011d1a7020000e829fd11/content.htm
Regards,
Kiron Kumar T.

Error in FI document creation

Hi,
I am trying to post excise document through J1IS but am getting the following error:
"Error in FI Document Create"
Message No. 8I031
Kindly help
Regards.

HellO parin.
Your Problem Will be Resolved Only after Uploading Patch 601, 602, 603, 604, 605.
Please Follow 1434628 note
Regard,
Riten patel

Error in accounting document creation

Hello All,
While releasing the billing document, getting the following error:
<b>SYST: Tax jurisdiction code at lowest level not transferred
Message no. FF793
Diagnosis
The application has not transferred the tax jurisdiction code at the lowest level (TXJDP) to the Accounting interface.</b>
Can someone help me as to what the error is and how to rectify the same.
Thanks,
Gopal

Gopal,
check Tax Jurisdiction Code

Error in Billing Document creation in case of STO !!

Hi Friends,
I am facing one error
While Creating billing document (With combination of STO billing document type and STO delivery type )against outbound delivery in case of STO system is giving error msg The Item is not relevant to Billing
Need your valuable suggestions
Regards
Vivek

Hi,
If you are using delivery type "NL" or it copy in case of STO then you can not create Billing Document w.r.t. this. Also, Billing Document is not to be created in case of STO (B/w plants of same compnay code). In this case you have to create Pro-forma Invoice which will not have any Accounting effect and will be used for reference purpose to send it along with goods.
In VF01, enter Delivery No and select Billing Type as "F8" (Pro-forma Invoice) and then prceed further.

Error in Accoounting document creation

Hi Experts,
While releasing an SD-Billing Doc to acounting, we are receiving an Error "At least one line item of the sending company code must exist "
This is for all Co.Codes and all Customers and materials.
Please suggest what may be the reason for the same.
Regards
Montee

Hi,
i'm having exactly the same problem, while trying to register a document in accounting.
The transaction we use is FBV1 and we keep getting this FP042 error, which we're unable to debug.
Do you have any clue about what's happening behind SAP scenes with this error?
Thanks,
Best regards.

Changes to financial document are only visible after reassign the financial document to sales order

Hello experts,
Whenever I am changing a financial document ( say validity date) in
vx12n, I want the same to get reflected in the sales documents to which
the financial document is already attached.
Currently to make the change visible I have to reassign the financial
document in the sales document.
Reassign is not possible in the cases where part delivery already been
happened (LC fields got grayed out ).
We dont want to run sensitive T CODES like VKM3 or VKM4 due to audit
related issues .
Is there any way so that any change in financial document is
automatically captured in the related sales document.
Regards
Avik

Hi Minhaj ,
Thanks for your reply . But the same is happening @IDES also. As per as my business scenario , in the time of creating the financial document by VX11N , user does not know when the sales order is going to be delivered. By the time of delivery , validity date or some other FD fields get changed in VX12N to accommodate the requirements . When they are trying to deliver the same from the sales order , credit check is throwing error for the same fields which are already changed . Now after reassign the same , credit check is allowing to deliver . But in worst possible scenarios ,it may happens validity date of the FD get expired when part delivery is already completed . Thus make the FD fields of sales document non-modifiable . You cant reassign the same any more.
As per as your reply relating to Basis , please share some specific information so that I can communicate them effectively .
Regards
Avik

Financial Documents and Credit Block

Hi all,
I am facing an issue wit Financial documents. I have a customer code who has exceeded his credit limit. Now for one of the Sales Order he has submitted LC, which was created as Financial document in VX11N. This FD is linked to Sales order at Header and Item level as per the process. But still Credit check is happening and the Sales document is gettng blocked for Credit.
As per my understanding, if a FD is attached, system will check the value of the Sales document with the Value of the FD and if the order value exceeds the FD value, then the document will be blocked.
Where can be the issue. Please advise.
Regards,
Ajit P

Hiii
your FD or LC is kind of Noted Item, Now if you want to use that into credit limit you have to do following
T-Code FBKP
Double click on "Special G/L"
Double Click on relevent G/L indicator L or R or according to ur required LC indicator (Please take help of FI)
Give you Chart of Area
In G/L assigment screen -
click on GOTO on menu and click on properties
Now check the indicator "Relevant for Credit limit"
Regards
Shambhu Sarkar

Financial Document results not OK

Hi All,
I have one issue that when user enters the Financial documentno in the sales order its giving the error.
Financial document is for LC ( Letter of credit )
Financial Document:Check::Deadlines Check result : Not OK
Message NO E1574
Diagnosis:
According to the seetings in the customization for financial documentsThe system is checked the details;
Check : Deadlines
latest ship date : 31.07.2010
last confirmed schedule lines : 05.08.2010
check results : Not OK
When i checked the dates in the Financial document
latest ship date is 20.07.2010
But in the order delivery dates GI, Material availability,loading are 10.07.2010.
Kindly help..
Regards,
SK
Edited by: Mastan Shaik on Jun 17, 2010 11:52 AM

Dear Mastan,
Flow the seteps:
1. Please check the where you have assigned your Financial Document (LC) in Sales Order either Header Level or Item
Enter the FD at Header Level
Menupath: VA01/VA02 Goto Header Data - Billing - Financial Document Number
2. Please check the Schedule line date
Menupath: VA02 - GOTO - ITEM - SCHEDULE LINE- CHECK THE DATE
If the date is in future month as you mentioned in the mail 05.08.2010 and Last ship date is 31.07.2010 so you have to change the of FD by going into change mode.
3. Do changes in your Financial Documents VX12N Accordingly.
Best Regards,
MH

Error while creation financial document while cancellation

Dear all,
After reversing the invoice, the financial accounting document is not getting saved. It is giving error message to select a particular number range. But after this invoice a few more invoices were reversed and the system has not issued any error messages and financial document also has been generated successfully. Now I want to debug the program to check what could have went wrong while generating this particular invoice with the error message.
Request you to advice me when exactly does the system assigns the number internally to the financial document to set the break point at that level and hence probably will be able to resolve the issue. I have tried to take the help of my abaper but am unsuccessful in finding out the error. please do the needful.
Thanks,
Andy.

Dear Ahemmed,
The error message is pasted below
VF11 is the T-code used for cancellation of the invoice.
And for document type RV, please find the screen shot below
For reverse document type VR,
Thanks,
Andy

User exit when saving the financial document (VX11N)

Hi,
We are creating financial document as a letter of credit using transaction code VX11N. User would like to have some checking on the fields based on some user defined logic. Is there any user exit that can be used to serve this purpose. I am looking to usre exit similar to when saving sales order (i.e: USEREXIT_SAVE_DOCUMENT in MV45AFZZ).
Regards

Hi,
Check below link for all SD user Exits.
https://wiki.sdn.sap.com/wiki/display/ERPLO/SDUserexits
Best regards,
Anupa

Bapi-salesorder creation error in creating document

hai friends..
iam doing creation of sales order using bapi .-structures..
but error in creating doucment ....
can u send me some example .. abt sales order .creation ..
once u check my code ...
DATA: BEGIN OF HEADER OCCURS 0,
       VBELN LIKE BAPIVBELN-VBELN,
       AUART LIKE VBAK-AUART,
       VKORG LIKE VBAK-VKORG,
       VTWEG LIKE VBAK-VTWEG ,
       SPART LIKE VBAK-SPART,
       VKBUR LIKE VBAK-VKBUR,
       KUNNR LIKE BAPIPARNR-PARTN_NUMB ,"vbak-kunnr,
    END OF HEADER.
DATA: BEGIN OF ITEM OCCURS 0,
       VBELN LIKE BAPIVBELN-VBELN,
       POSNR LIKE BAPISDITM-ITM_NUMBER ,"vbap-posnr,
       MATNR LIKE VBAP-MATNR,
      NETWR LIKE VBAP-NETWR,
       KWMENGE LIKE VBAP-KWMENG,
      WERKS LIKE VBAP-WERKS,
      NETPR LIKE VBAP-NETPR,
   END OF ITEM.
DATA: ORDER_HEADER_IN LIKE BAPISDHD1,
       ORDER_HEADER_INX LIKE BAPISDHD1X.
DATA: ITAB_HEAD likE order_header_in,
      ITAB_HEADX likE ORDER_HEADER_INX.
DATA: ITAB_ITEM TYPE STANDARD TABLE OF BAPISDITM WITH HEADER LINE,
      ITAB_ITEMX TYPE STANDARD TABLE OF BAPISDITMX WITH HEADER LINE.
DATA: KUST TYPE STANDARD TABLE OF BAPIPARNR WITH HEADER LINE,
       RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA: VNO LIKE BAPIVBELN-VBELN,
      VCNT LIKE VBAP-POSNR.
LOOP AT HEADER.
    VCNT = 10.
    CLEAR ITAB_HEAD.
   ORDER_HEADER_IN-REFOBJTYPE = 'OR'.
   ORDER_HEADER_IN-REFOBJKEY = 'OR'.
   ORDER_HEADER_IN-REFDOCTYPE = 'OR'.
   ORDER_HEADER_IN-DOC_TYPE = HEADER-AUART.
    ITAB_HEAD-DOC_TYPE = HEADER-AUART.
    ITAB_HEAD-SALES_ORG = HEADER-VKORG.
    ITAB_HEAD-DISTR_CHAN = HEADER-VTWEG.
    ITAB_HEAD-DIVISION = HEADER-SPART.
    ITAB_HEAD-SALES_OFF = HEADER-VKBUR.
    KUST-PARTN_NUMB = HEADER-KUNNR.
     ITAB_HEADX-DOC_TYPE = 'X'.
     ITAB_HEADX-SALES_ORG = 'X'.
    ITAB_HEADX-DISTR_CHAN = 'X'.
    ITAB_HEADX-DIVISION = 'X'.
    ITAB_HEADX-SALES_OFF = 'X'.
    LOOP AT ITEM WHERE VBELN = HEADER-VBELN.
      REFRESH RETURN.
      ITAB_ITEM-ITM_NUMBER = VCNT.
      ITAB_ITEM-MATERIAL = ITEM-MATNR.
      ITAB_ITEM-NET_WEIGHT = ITEM-KWMENGE.
      APPEND ITAB_ITEM.
      ITAB_ITEMX-ITM_NUMBER = VCNT.
      ITAB_ITEMX-MATERIAL = 'X'.
      ITAB_ITEMX-NET_WEIGHT = 'X'.
      APPEND ITAB_ITEMX.
      VCNT = VCNT + 10 .
    ENDLOOP.
    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
      EXPORTING
    SALESDOCUMENTIN               = SALESORDER
        ORDER_HEADER_IN              = ITAB_HEAD
     ORDER_HEADER_INX              = ITAB_HEADX
    SENDER                        =
    BINARY_RELATIONSHIPTYPE       =
    INT_NUMBER_ASSIGNMENT         =
    BEHAVE_WHEN_ERROR             =
    LOGIC_SWITCH                  =
    TESTRUN                       =
    CONVERT                       = ' '
     IMPORTING
       SALESDOCUMENT                 = VNO
      TABLES
       RETURN                        = RETURN
       ORDER_ITEMS_IN                = ITAB_ITEM
       ORDER_ITEMS_INX               = ITAB_ITEMX
        ORDER_PARTNERS                = KUST.
   CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          WAIT          = 'X'.
         IMPORTING
           RETURN        = RETURN.
LOOP AT return WHERE type = 'E' OR type = 'A'.
EXIT.
ENDLOOP.
IF sy-subrc = 0.
WRITE: / 'Error in creating document'.
ELSE.
COMMIT WORK AND WAIT.
ENDIF.
    WRITE: / '   Sales Order NO IS: ', VNO.
    WRITE: / SPACE.
    CLEAR VNO.
    WRITE SY-ULINE.
ENDLOOP.
my HEader is    123    OR 1000 30 10 SATYA.
ITem 2 IS     123   10 HAI   15
once u check it ......

Hi Satya,
just check this
REPORT Z_STANDARD_SALES_ORDER no standard page heading.
DATA DECLARATION
CONSTANTS : C_X VALUE 'X'.
Structures to hold Sales order header data
DATA : HEADER LIKE BAPISDHD1," OCCURS 0 WITH HEADER LINE,
       HEADERX LIKE BAPISDHD1X." OCCURS 0 WITH HEADER LINE.
Internal Tables to hold Sales order ITEM DATA
DATA : ITEM LIKE BAPISDITM OCCURS 0 WITH HEADER LINE,
       ITEMX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE.
Internal Tables to hold Partners ITEM DATA
DATA : PART LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE.
Internal Tables to hold Partners SCHEDULE DATA
DATA: SCHEDULE LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE,
      SCHEDULEX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE.
Internal table to hold messages from BAPI call
DATA: RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA W_MSG(150).
*DATA: begin of wa_MESSAGE,
     message(150),
     end of wa_message.
*DATA: itab_msg like table of wa_message with header line.
Data: Begin of Record occurs 0,
      Control type i,
      DOC_TYPE like HEADER-DOC_TYPE,
      SALES_ORG like HEADER-SALES_ORG,
      DISTR_CHAN like HEADER-SALES_ORG,
      DIVISION like HEADER-DIVISION,
      PURCH_NO_C like HEADER-PURCH_NO_C,
      PARTN_NUMB like PART-PARTN_NUMB ,
      PARTN_ROLE like PART-PARTN_ROLE ,
      ITM_NUMBER like ITEM-ITM_NUMBER,
      MATERIAL like ITEM-MATERIAL,
     TARGET_QTY like item-TARGET_QTY,
      REQ_QTY LIKE BAPISCHDL-REQ_QTY,
      TARGET_QU like item-TARGET_QU,
      PLANT like ITEM-PLANT,
      PMNTTRMS like header-PMNTTRMS,
      End of record.
data: itab like ALSMEX_TABLINE occurs 0,
      wa like ALSMEX_TABLINE.
data: SO like BAPIVBELN-VBELN.
Selection Screen
selection-screen begin of block b1 with frame title text-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
selection-screen end of block b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
PERFORM GET_FILE USING P_FILE.
Start of Selection
start-of-selection.
DATA: xl type string.
xl = '*.xls'.
IF not P_FILE CP xl.
    Message 'Wrong input file format' type 'E'.
ENDIF.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      FILENAME                      = P_FILE
      I_BEGIN_COL                   = 1
      I_BEGIN_ROW                   = 1
      I_END_COL                     = 13
      I_END_ROW                     = 3000
    TABLES
      INTERN                        = itab
EXCEPTIONS
INCONSISTENT_PARAMETERS       = 1
UPLOAD_OLE                    = 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.
DATA POPULATION
loop at itab into wa.
    if wa-col = '0001'.
      record-Control = wa-value.
    elseif wa-col = '0002'.
      record-DOC_TYPE = wa-value.
    elseif wa-col = '0003'.
      record-SALES_ORG = wa-value.
    elseif wa-col = '0004'.
      record-DISTR_CHAN = wa-value.
    elseif wa-col = '0005'.
      record-DIVISION = wa-value.
    elseif wa-col = '0006'.
      record-PURCH_NO_C = wa-value.
    elseif wa-col = '0007'.
      record-PARTN_NUMB = wa-value.
    elseif wa-col = '0008'.
      record-PARTN_ROLE = wa-value.
    elseif wa-col = '0009'.
      record-PMNTTRMS = wa-value.
    elseif wa-col = '0010'.
      record-ITM_NUMBER = wa-value.
    elseif wa-col = '0011'.
      record-MATERIAL = wa-value.
    elseif wa-col = '0012'.
      record-REQ_QTY = wa-value.
    elseif wa-col = '0013'.
      record-TARGET_QU = wa-value.
    elseif wa-col = '0014'.
      record-PLANT = wa-value.
    endif.
    AT END OF row.
      APPEND record.
      CLEAR: wa, record.
    ENDAT.
endloop.
DATA: tot_lines type i,
        tot_po type i,
        index type i.
describe table record lines tot_lines.
read table record index tot_lines.
tot_po = record-control.
DO tot_po times.
    index = index + 1.
    clear: HEADER,HEADERX,ITEM[],ITEMX[],RETURN,RETURN[],SCHEDULE[],SCHEDULEX[], PART[],PART.
    refresh: ITEM[],ITEMX[],RETURN[],SCHEDULE[],SCHEDULEX[],PART[] .
POPULATE HEADER FLAG.
    HEADERX-UPDATEFLAG = c_x.
    HEADERX-doc_type = c_x.
    HEADERX-SALES_ORG = c_x.
    HEADERX-DISTR_CHAN = c_x.
    HEADERX-DIVISION = c_x.
    HEADERX-PURCH_NO_C = c_X.
    HEADERX-PMNTTRMS = c_X.
    loop at record where control = index.
POPULATE HEADER DATA FOR PO
      HEADER-DOC_TYPE = record-DOC_TYPE.
      HEADER-SALES_ORG = record-SALES_ORG.
      HEADER-DISTR_CHAN = record-DISTR_CHAN.
      HEADER-DIVISION = record-DIVISION.
      HEADER-PURCH_NO_C = record-PURCH_NO_C.
      HEADER-PMNTTRMS = record-PMNTTRMS.
*POPULATE ITEM DATA.
      ITEM-ITM_NUMBER = record-ITM_NUMBER.
      ITEM-MATERIAL = record-material.
     ITEM-TARGET_QTY = record-TARGET_QTY.
      ITEM-TARGET_QU = record-TARGET_QU.
      ITEM-PLANT = record-PLANT .
      APPEND ITEM.
*POPULATE ITEM FLAG TABLE
      ITEMX-ITM_NUMBER = record-ITM_NUMBER.
      ITEMX-UPDATEFLAG = C_X.
     ITEMX-TARGET_QTY = C_X.
      ITEMX-PLANT = C_X .
      ITEMX-MATERIAL = C_X .
      ITEMX-TARGET_QU = C_X .
      APPEND ITEMX.
*POPULATE SCHEDULE TABLE
      SCHEDULE-ITM_NUMBER = RECORD-ITM_NUMBER.
      SCHEDULE-REQ_QTY = RECORD-REQ_QTY.
      APPEND SCHEDULE.
*POPULATE SCHEDULE TABLE
      SCHEDULEX-ITM_NUMBER = RECORD-ITM_NUMBER.
      SCHEDULEX-REQ_QTY = C_X.
      APPEND SCHEDULEX.
    endloop.
*POPULATE PARTNER TABLE
    PART-PARTN_NUMB = record-PARTN_NUMB.
    PART-PARTN_ROLE = record-PARTN_ROLE.
    APPEND PART.
*BAPI CALL
    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
          EXPORTING
           ORDER_HEADER_IN               = HEADER
           ORDER_HEADER_INX              = HEADERX
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
          IMPORTING
           SALESDOCUMENT                 = SO
          TABLES
           RETURN                        = RETURN
           ORDER_ITEMS_IN                = ITEM
           ORDER_ITEMS_INX               = ITEMX
           ORDER_PARTNERS                = PART
           ORDER_SCHEDULES_IN            = SCHEDULE
           ORDER_SCHEDULES_INX           = SCHEDULEX
ORDER_CONDITIONS_IN           =
ORDER_CONDITIONS_INX          =
ORDER_CFGS_REF                =
ORDER_CFGS_INST               =
ORDER_CFGS_PART_OF            =
ORDER_CFGS_VALUE              =
ORDER_CFGS_BLOB               =
ORDER_CFGS_VK                 =
ORDER_CFGS_REFINST            =
ORDER_CCARD                   =
ORDER_TEXT                    =
ORDER_KEYS                    =
EXTENSIONIN                   =
PARTNERADDRESSES              =
    loop at return where type = 'E' and ID NE 'MEPO' and ID NE 'BAPI'.
      WRITE:/ Return-message.
    endloop.
*Confirm the document creation by calling database COMMIT
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT = 'X'.
*Messages
    loop at return where type = 'S' and number ne '233'.
     WRITE:/ Return-message.
      CALL FUNCTION 'FORMAT_MESSAGE'
        EXPORTING
          ID        = return-ID
          LANG      = SY-LANGU
          NO        = return-NUMBER
        IMPORTING
          MSG       = W_MSG
        EXCEPTIONS
          NOT_FOUND = 1
          OTHERS    = 2.
      WRITE W_MSG.
     itab_msg-message = w_msg.
     append itab_msg.
      clear: W_MSG.
    ENDLOOP.
enddo.
     -->P_W_FILE text
FORM GET_FILE USING    P_W_FILE.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
    CHANGING
      FILE_NAME     = P_W_FILE
    EXCEPTIONS
      MASK_TOO_LONG = 1
      OTHERS        = 2.
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.     "GET_FILE
Regards,
Sachin

I am facing problem document creation the error is Message no. 3G103

i am facing problem document creation the error is Message no. 3G103

Dear Satish,
Usually this error is due to a wrong customizing.
Go through note 1594322 and 179655 will help you to make an analysis of this issue, you should created an excel file for each wage type which should be posted as it is showed in the note.
1594322 Error message 3G103 in RPCIPE00 & RPCIPE01 'Posting balance is
not cleared' 179655 RPCIPE00:Rejectn, employee w.posting bal.not clrd
Best Regards,
Deepak.

VX11N - FInancial Document Assignmnet to delivery or sales order

Hi all,
First we do not activated the credit check at Delivery and PGI levels.
But in case of export scenarios we are using LC documents, and these documents are some times attached to delivery and some times to sales order.
Case1: The sales order is blocked due to credit check and released, then user creates a delivery, then follows up with LC documents creation. Here the delivery document is blocked due to financial document status is not 'D'. Initially the LC document status is 'B' due to incompletion, i have completed the document, even though the status remains 'B' and not releasing the delivery from credit block. Users are forced to release it using VKM1 t code.
Case 2: The customer is in his credit limits, and a sales order is created, then in change mode user creates a LC document for this SO, system automatically brings this SO in to credit block saying the pop up message, financial document status is not 'D'.
In both the cases system message is EI 574, and asking us to change the status of financial document to 'D', but this is system controlled status we can not change it manually. Also asking us to check at Foreign tradedocumentary paymentsbasic settings, i did not find proper settings here, if any one knows about it please advise.
I have checked the risk management settings: This item category is activated for credit check, but this is a required setting to update the open items for credit check which we use in automatic credit check.
Our requirement is sales order or a delivery should not get blocked due to the financial document and should not obstruct the user to process it further.
Experts your comments please ASAP.
Venkat

FInancial Document Assignmnet to delivery or sales order
Ideally speaking and to answer this question, LC should always be assigned to sale order only. In exports scenarios, customer will release LC against one order and not against multiple deliveries. One of the L/C condition will be "Partial Shipment Allowed" in which case only, you are suppose to generate multiple deliveries.
Of course, there will be instances where customer will amend the existing LC due to some reasons but he will never open fresh LCs against delivery.
thanks
G. Lakshmipathi

Error in financial document creation vx11n

Similar Messages

Maybe you are looking for