Delivery Note to Subcontract creation error "Essential transfer parameters

Hi
I am facing issue in return delivey
Delivery Note to Subcontract creation error "Essential transfer parameters are missing in record:000001".
Could you please let me know the casue of this error and where exactly i can see error.
Regards
vikcy

Hi Vicky,
Check If the Customer number(Plant) has been maintained in the vendor master record control data and the vendor should also be maintained in the customer master data. Once you maintain this system determines the shipping point based on the customer master and the shipping data missing. Kindly try delivering after maintaining these and let me know If you need any more information on this.
Regards
Ram Pedarla

Similar Messages

Error in Delivery using ME2O : "essential transfer parameters are missing"

Hi All
We have a subcontracting PO for which when trying to create Delivery using ME2O we are getiing error "essential transfer parameters are missing in record 000001". I understand that this error is coming because shpping point is not ap[earing when click on create delivery tab.
Any pointer in this regrd.
Would like to inform that we have already connected the Vendor and Customer in respective master. Apart from that
we have checked that shipping condition, loading group and plant is also set which determines the shipping point.
Would appreciate usefule pointer as this is very urgent.
Rgrds
Yogesh

Hi,
Check following;
OVX6 - Assign sales organization - distribution channel - plant
SPRO > MM > Purchasing > Purchase Order > Set Up Subcontract Order > Here assign Delivery Type "LB" to Plant
SPRO > MM > Purchasing > Purchase Order > Set Up Stock Transport Order > Define Shipping Data for Plants > Here assign the Customer Code of Plant and Sales Area to the Plant
Note: - Customer Code of Plant is to be created in XD01.
Check whether Material Master is extended to the Sales Area.
OVL2 - Cross-check Shipping Point Determination

Essential transfer parameters are missing in record: 000001

I have been trying to create a delivery ( Type LB) trough ME2O and get
this error .
Essential transfer parameters are missing in record: 000001
Message no. VL 561
Diagnosis
Information necessary for this delivery is missing.
System Response
Depending on the category of the delivery being created, the system
needs the following transfer data:
Outbound delivery::::::::
Shipping point
Sales organization
Distribution channel
Division
Material number
Delivery quantity
Ship-to party
Base unit of measure
Inbound Delivery::::::::::::::::::
Base Unit of Measure
Conversion factors for converting base and sales units
Goods Receiving Point
Outbound and inbound deliveries from goods movements::::::
Plant and sales unit transfer data is always mandatory..
Please help me how to fix this issue.
Thanks in advance

hi,
Do check whether the below points are mentioned or not...
Outbound delivery
Shipping point
Sales organization
Distribution channel
Division
Material number
Delivery quantity
Ship-to party
Base unit of measure
Inbound Delivery
Base Unit of Measure
Conversion factors for converting base and sales units
Goods Receiving Point
If it is given here in the doc, then check whether these are getting saved into the table or not..
Tables are :
LIKP, LIPS, VTTP...
Hope it helps..
Regards
Priyanka.P

IDOC in 51 status.Essential transfer parameters are missing in record

Hi All,
Essential transfer parameters are missing in record: 8701 000001
Message no. VL561
I am not understanding what is missing in the IDOC.
Please help me in resolving the issue.
Thanks,
Forum

hi,
Do check whether the below points are mentioned or not...
Outbound delivery
Shipping point
Sales organization
Distribution channel
Division
Material number
Delivery quantity
Ship-to party
Base unit of measure
Inbound Delivery
Base Unit of Measure
Conversion factors for converting base and sales units
Goods Receiving Point
If it is given here in the doc, then check whether these are getting saved into the table or not..
Tables are :
LIKP, LIPS, VTTP...
Hope it helps..
Regards
Priyanka.P

Essential Transfer Parameters Missing in record during Inbound IDOC process

Dear Gurus
We are creating a Inbound delivery in one system, we have made all the custom settings for IDOC processing for inbound and outbound idoc in both the systems. Upon the execution of inbound delivery, the system
During the Inound delivery processing, the outbound IDOC is successfully distributed. However in the receving system, the IDOC is not posted and it throws the below erroe\r
Essential transfer parameters are missing in record: 0180000055 000010 / Mess number 561 and message type E
We are using Outbound IDOC mess type DESADV basic type DELVRY01 process code DELV with FM IDOC_OUT PUT_DELVRY
In the receiving system message type DESADV , process code DELS, and FM IDOC_INPUT_DESADV1
What is that which is going wrong.
Please help me out
Thanks

Hello
To create inbound delivery from outbound delivery, use following setting -
Outbound idoc -
idoc type - DESADV01
message type - DESADV
Process code - SD05
FM - IDOC_OUTPUT_DESADV01
Inbound iDOC -
Message Type - DESADV
Process Code - DESA
FM - IDOC_INPUT_DESADV
Idoc Type - DESADV01

Essential transfer parameters missing while GR into a HU managed Sloc.

Hi Gurus,
I am doing GR into a HU managed storage location. I am expecting the system to create an inbound delivery & HU internally. But the error is
"Essential transfer parameters are missing in record: 45000XXXXX 000010 Message no. VL561".
in IMG-Shipping I have maintained "Assign Goods Receiving Points for Inbound Deliveries". I dont know whether Packing instruction determination is necessary for this, but I have done that also.
Please let me know where I am missing
Nagesh

Hi,
That's new for me. What is then the use of the inbound delivery if you do the GR on the PO with MIGO?
Standard process:
GR on PO through MIGO
GR on inbound delivery through VL32N or MIGO (or VL36/ BORGR).
Required for usage of inbound deliveries:
confirmation control key in the PO (defaulted through vendor) which requires an inbound delivery.
MdZ

Create delivery in subcontracting - Essential transfer parameters missing

Hi Guys,
This is my first thread - I hope I get everything right
From ME2O, stock monitoring for Vendor (subcontracting), I want to create a delivery to the vendor. After checking a material with a requirement and pressing "Create delivery" I get a box containing:
Vendor:
material:
Plant:
Shipping Point:
Stor. location:
Batch:
Quantity:
All fields are predefined and filled except "Shipping point". It's grayed so I can't search/enter it manually. I have assigned a loading group to the material in the Material Master: Sales: General/Plant. So where does this (missing) value come from if not the loading group?
Hoping for an answer
/Thomas

Hi Thomas,
The shipping pt has to maintained in customizing
spro>logistics execution> shipping>basic shipping fns>shipping pt and GR pt determination
maintain the shipping pt here for your plant and try again.
Hope this helps
regards
Anand.C

How to create excise invoice with refer to Delivery Note

Hi SAP Expert,
I am doing STOCK Transport process from factory to depot and hitting error while creating excise invoice in Factory.
From SAP help on Creating Excise Invoice, it said :
From the SAP Easy Access screen, choose Indirect Taxes ® Sales/Outbound Movements ® Excise Invoice ® For Sales Order ® Outgoing Excise Invoice Create/Change/Display ®
If you want to create the excise invoice with reference to a pro forma excise invoice or commercial invoice, choose Excise Invoice ® Create.
If you want to create the excise invoice with reference to a delivery note, choose Exc. inv. for delivery ® Create.
Enter the number of the reference document.
- When i created the excise invoice with reference to a STO Delivery Note, i am getting error : " For delivery 800050092 no document of type JEX exist "
- I already setup the config to assign Delivery Type NL to billing type JEXP.
I was doing the steps as below :
1. ME21N u2013 Create Stock Transport Order
2. VL10B u2013 Create Outbound Delivery w.r.t. STO
3. J1IIN u2013 Create Outgoing Excise Invoice w.r.t. Delivery Note
- Anything that i am missing ?

Hi Guru,
Thanks for your reply. It is my typo error. I have maintained the delivery type NL to billing type JEX, instead of JEXP
I am getting error :
For delivery 800050092 no document of type JEX exist
Message no. 8I320
Diagnosis
The excise reference document defined does not exist for the delivery.
Procedure
Create the excise reference document before running the excise posting transaction.
- What is it means by create the excise reference document before running the excise posting transaction ? Do I need to create Pro-forma invoice prior to execute transaction J1IIN ?
I did not check the selection for ": Excise Inv during Billing " in my Excise Group maintainance.

Automatic form generation on creation transfer order for delivery note?

Hi,
I have to create a form that should automatically be generated on the creation of a transfer order for delivery note. How do I trigger this automatic creation of the form? And how can the transfer order number be passed to my print program?
Thx!

hi christophe,
To issue the delivery output, go to transaction VL02N.
Then go to EXTRAS-> OUTPUT->HEADER->EDIT
In the Message output screen enter the relevant output type created for the delivery.
Choose the relevant medium of output.
Choose Simple Mail, in this case the field NAST-NACHA will be having a value of 7.
Specify the Partner Function; in this case it is MA -> Mail partner address
Select the Communication Method for the output type maintained.
This will take you to the SAPOFFICE screen.
Enter there the E-Mail Address to which you want to send the delivery document as PDF.
A mail will be sent to the e-mail address of the E-Mail Address specified, with the delivery output form as a PDF attachment.
hope it will help u ..
*& Report ZZ_TEST                                                     *
REPORT zz_test                                 .
INCLUDE zz_test_top.
INCLUDE zz_test01.
      FORM entry                                                    *
--> RETURN_CODE                                                   *
--> US_SCREEN                                                     *
FORM entry USING return_code us_screen.
CLEAR retcode.
xscreen = us_screen.
PERFORM processing USING us_screen.
CASE retcode.
    WHEN 0.
      return_code = 0.
    WHEN 3.
      return_code = 3.
    WHEN OTHERS.
      return_code = 1.
ENDCASE.
ENDFORM.                    "entry
*& Include           ZZ_TEST_TOP                                      *
TABLES : nast,
           tnapr.
TYPES : BEGIN OF t_SOUDNAMEI1.
        INCLUDE STRUCTURE SOUDNAMEI1.
TYPES : END OF t_SOUDNAMEI1.
Internal Table declarations
DATA: i_otf TYPE itcoo OCCURS 0 WITH HEADER LINE,
i_tline TYPE TABLE OF tline WITH HEADER LINE,
i_receivers TYPE TABLE OF somlreci1 WITH HEADER LINE,
i_record LIKE solisti1 OCCURS 0 WITH HEADER LINE,
*Objects to send mail.
i_objpack LIKE sopcklsti1 OCCURS 0 WITH HEADER LINE,
i_objtxt LIKE solisti1 OCCURS 0 WITH HEADER LINE,
i_objbin LIKE solisti1 OCCURS 0 WITH HEADER LINE,
i_reclist LIKE somlreci1 OCCURS 0 WITH HEADER LINE,
i_lips LIKE lips OCCURS 0 WITH HEADER LINE,
i_SOUDNAMEI1 TYPE STANDARD TABLE OF t_SOUDNAMEI1.
Work Area declarations
DATA:w_objhead TYPE soli_tab,
wa_control_parameters TYPE ssfctrlop,
wa_output_options TYPE ssfcompop,
w_return TYPE ssfcrescl,
w_doc_chng TYPE sodocchgi1,
w_data TYPE sodocchgi1,
w_buffer TYPE string,"To convert from 132 to 255
wa_SOUDNAMEI1 TYPE t_SOUDNAMEI1,
Variables declarations
w_form_name TYPE rs38l_fnam,
w_len_in LIKE sood-objlen,
w_len_out LIKE sood-objlen,
w_len_outn TYPE i,
w_lines_txt TYPE i,
w_lines_bin TYPE i,
retcode      TYPE sy-subrc,
xscreen      TYPE c,
w_spld TYPE usr01-spld,
w_receiver TYPE SOXNA-FULLNAME,
w_OBJ_RECORD TYPE OBJ_RECORD,
w_user type sy-uname,
w_email TYPE ad_smtpadr.
Constants Declaration
CONSTANTS : c_x TYPE c VALUE 'X',
              c_atrate(1) TYPE c VALUE '@'.
*& Include           ZZ_TEST01                                        *
      FORM PROCESSING                                               *
FORM processing USING proc_screen.
SELECT * FROM lips
    INTO TABLE i_lips
    WHERE vbeln = nast-objky.
Call Function module to Getfunction Module name Generated by Smartform
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      formname           = tnapr-sform
    IMPORTING
      fm_name            = w_form_name
    EXCEPTIONS
      no_form            = 1
      no_function_module = 2
      OTHERS             = 3.
IF sy-subrc <> 0.
    retcode = sy-subrc.
ENDIF.
CLEAR : wa_control_parameters,
          wa_output_options.
CASE nast-nacha.
    WHEN '1'.
      wa_control_parameters-device    = 'PRINTER'.
    WHEN '7'.
      DATA: l_email TYPE ad_smtpadr.
      wa_output_options-tdnoprev = c_x.
      wa_control_parameters-getotf = c_x.
To get the default output device maintained in the
User profile
     SELECT SINGLE spld FROM usr01
      INTO w_spld
      WHERE bname EQ nast-usnam.
      IF sy-subrc EQ 0.
        MOVE w_spld TO wa_output_options-tddest   .
      ENDIF.
      wa_output_options-tdnoprev = c_x.
      wa_control_parameters-getotf = c_x.
To get the email address maintained for the particular output
      CALL FUNCTION 'NAST_GET_MESSAGE_OBJECT_RECV'
        EXPORTING
          pi_objkey             = nast-tdname
        IMPORTING
          pe_addr               = w_receiver
        CHANGING
          pc_objhandle          = w_obj_record
        EXCEPTIONS
          maildata_not_readable = 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.
      IF w_receiver NA c_atrate.
To retrieve the E-Mail Id in case we get the User name from NAST
        CLEAR wa_soudnamei1.
        REFRESH i_soudnamei1.
        MOVE w_receiver TO wa_soudnamei1-fullname.
To get the user name
        CALL FUNCTION 'SO_NAME_CONVERT_API1'
          EXPORTING
            name            = wa_soudnamei1
          TABLES
            names           = i_soudnamei1
          EXCEPTIONS
            user_not_exist = 1
            parameter_error = 2
            x_error         = 3
            OTHERS          = 4.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        CLEAR wa_soudnamei1.
        READ TABLE i_soudnamei1 INTO wa_soudnamei1 INDEX 1.
        MOVE wa_soudnamei1-sapname TO w_user.
To get the e-mail Id maintained in the user profile
        CALL FUNCTION 'FTR_CORR_CHECK_EMAIL_SAP_USER'
          EXPORTING
            i_user              = w_user
          IMPORTING
            e_email_address     = l_email
          EXCEPTIONS
            mail_address        = 1
            determination_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.
        MOVE l_email TO w_receiver.
      ENDIF.
      MOVE w_receiver TO w_email.
ENDCASE.
wa_control_parameters-no_dialog = c_x.
wa_control_parameters-langu     = nast-spras .
wa_output_options-tdteleland    = nast-tland.
wa_output_options-tdtelenum     = nast-telfx .
wa_output_options-tdsenddate    = nast-erdat .
wa_output_options-tdsendtime    = nast-eruhr .
wa_output_options-tddataset     = nast-dsnam .
wa_output_options-tdsuffix1     = nast-dsuf1 .
wa_output_options-tdsuffix2     = nast-dsuf2 .
wa_output_options-tdimmed       = nast-dimme .
wa_output_options-tddelete      = nast-delet .
wa_output_options-tdautority    = nast-tdautority.
wa_output_options-tdcovtitle    = nast-tdcovtitle .
wa_output_options-tdcover       = nast-tdocover .
wa_output_options-tdreceiver    = nast-tdreceiver.
wa_output_options-tddivision    = nast-tddivision.
wa_output_options-tdcopies      = nast-anzal .
wa_output_options-tdnewid       = c_x.
wa_output_options-tdarmod       = nast-tdarmod.
wa_output_options-tdnoarmch     = c_x.
CALL FUNCTION w_form_name
    EXPORTING
     archive_index      = toa_dara
     archive_parameters = arc_params
      control_parameters = wa_control_parameters
      output_options     = wa_output_options
      user_settings      = ' '
    IMPORTING
      job_output_info    = w_return
    TABLES
      it_lips            = i_lips
    EXCEPTIONS
      formatting_error   = 1
      internal_error     = 2
      send_error         = 3
      user_canceled      = 4
      OTHERS             = 5.
IF nast-nacha EQ 7 AND sy-subrc EQ 0.
    i_otf[] = w_return-otfdata[].
    CALL FUNCTION 'CONVERT_OTF'
      EXPORTING
        format                = 'PDF'
        max_linewidth         = 132
      IMPORTING
        bin_filesize          = w_len_in
      TABLES
        otf                   = i_otf
        lines                 = i_tline
      EXCEPTIONS
        err_max_linewidth     = 1
        err_format            = 2
        err_conv_not_possible = 3
        OTHERS                = 4.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
Convert PDF from 132 to 255.
    LOOP AT i_tline.
Replacing space by ~
      TRANSLATE i_tline USING ' ~'.
      CONCATENATE w_buffer i_tline INTO w_buffer.
    ENDLOOP.
Replacing ~ by space
    TRANSLATE w_buffer USING '~ '.
    DO.
      i_record = w_buffer.
Appending 255 characters as a record
      APPEND i_record.
      SHIFT w_buffer LEFT BY 255 PLACES.
      IF w_buffer IS INITIAL.
        EXIT.
      ENDIF.
    ENDDO.
    REFRESH: i_reclist,
    i_objtxt,
    i_objbin,
    i_objpack.
    CLEAR w_objhead.
Object with PDF.
    i_objbin[] = i_record[].
    DESCRIBE TABLE i_objbin LINES w_lines_bin.
Document information.
    w_doc_chng-obj_name = 'Smartform'.
    w_doc_chng-expiry_dat = sy-datum + 10.
    CONCATENATE 'Delivery' 'Note'
    INTO w_doc_chng-obj_descr.
*w_doc_chng-obj_descr = 'Smart form output'.
    w_doc_chng-sensitivty = 'F'. "Functional object
    w_doc_chng-doc_size = w_lines_txt * 255.
Pack to main body as RAW.
Obj. to be transported not in binary form
    CLEAR i_objpack-transf_bin.
Start line of object header in transport packet
    i_objpack-head_start = 1.
Number of lines of an object header in object packet
    i_objpack-head_num = 0.
Start line of object contents in an object packet
    i_objpack-body_start = 1.
Number of lines of the object contents in an object packet
    i_objpack-body_num = w_lines_txt.
Code for document class
    i_objpack-doc_type = 'RAW'.
    APPEND i_objpack.
Packing as PDF.
    i_objpack-transf_bin = 'X'.
    i_objpack-head_start = 1.
    i_objpack-head_num = 1.
    i_objpack-body_start = 1.
    i_objpack-body_num = w_lines_bin.
    i_objpack-doc_type = 'PDF'.
    i_objpack-obj_name = 'Smartform'.
    CONCATENATE 'Delivery' 'Note' '.pdf'
    INTO i_objpack-obj_descr.
    i_objpack-doc_size = w_lines_bin * 255.
    APPEND i_objpack.
Document information.
    CLEAR i_reclist.
e-mail receivers.
    i_reclist-receiver = w_email.
    i_reclist-express = 'X'.
    i_reclist-rec_type = 'U'. "Internet address
    APPEND i_reclist.
sending mail.
    CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
      EXPORTING
        document_data              = w_doc_chng
        put_in_outbox              = 'X'
      TABLES
        packing_list               = i_objpack
        object_header              = w_objhead
        contents_bin               = i_objbin
   contents_txt               = i_objtxt
        receivers                  = i_reclist
      EXCEPTIONS
        too_many_receivers         = 1
        document_not_sent          = 2
        document_type_not_exist    = 3
        operation_no_authorization = 4
        parameter_error            = 5
        x_error                    = 6
        enqueue_error              = 7
        OTHERS                     = 8.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
ENDIF.
ENDFORM.                    "processing

There's an error while delivery note creation for STO order

There's an error while delivery note creation for STO order even stock available in unrestricted stock
Edited by: sharma aman on Nov 8, 2011 9:00 AM

Dear Sharma Aman,
Check whether the following link helps you.
Mesaage : while creation of delivery : An item with no delivery quantity .)
Please search in google with the error message and definitely you will get some older posts in SDN which is solved.
In that case , you need not wait for the solution as it is already available.
If the solution provided do not suit you, then post it in SDN so that it will be a learning for others.
Try to search in the forum or in google before posting further queries
Thanks & Regards,
Hegal K Charles

Subcontract PO error VU013 when creating delivery note using ME2o

FYI to the forum, I had a user getting error VU 013 "Document is incomplete: You cannot save the delivery" when attempting to create a delivery note to send components to a subcontract vendor using ME2o.
I spent quite a bit of time researching this on this site and did not find a solution to my problem. As it turns out, the issue was that this part had a serialization profile which required serial numbers to be assigned in the delivery note. Our workaround solution was to change the serialization profile to one which did not make it obligatory on the DN. We then issued the DN and manually assigned the serial number to it, then finally changed the material master back to the obligatory profile.
Ideally, we would have liked the error message to indicate exactly what made the document incomplete (i.e. missing serial number in this case). I am not sure how to do that. Also, I found information regarding activating enhancement for serial numbers in purchasing (in EhP4). Presumably, this would allow me to specify the serial number(s) of the components to be issued to the vendor in the purchase order, and therefore automatically copy this into the subsequent DN. I activated this functionality, but did not get it to work. (Serial number maintenance was not visible in my PO.)
If anyone has successfully dealt with either of these things (changing the error message, or activating the functionality) let me know. Otherwise, I will close the thread, as I just wanted to notify people of my findings regarding reasons for the error, and my workaround.

I think the solution from OSS note will help to know the exact reason of the VU013 error:
335504 - Not possible to save delivery because of VU013
and OSS note
1029482 - ME2O: ME 346, although serial number usage optional
gives more insight and suppress the error message

IDOC for transfer order for delivery note LT03

Hi All,
I need to generate an outbound IDOC upon transfer order creation in Tcode LT03.
I found there are two types of IDOC discussed in this forum before. One is the Canceling Transfer Order IDOC and another one is the Confirmation Transfer Order IDOC.
I'm not sure whether these relevant to what I need or not.
Can i know what FM, message type and basic type should I use for this situation?
(generate an outbound IDOC upon transfer order creation in Tcode LT03)
Please advice.
Thanks.
Best Regards,
JL
Message was edited by:
KAR SENG LAW

I found something here,
Someone is using FM: L_IDOC_INPUT_WMTORD, message type WMTORD and basic type WMTOID01 in doing this when trying to send an Idoc to an external system when a transfer order for a delivery note is created (LT03). Is it OK ?
need advice.
Thanks again.

LT03 transfer order for delivery note

Hi Guys,
I try to execute the transfer order for delivery note with Lt03 after saving my delivery, but i got the error message No item that are to be picked were found. Ho can i solve that?
Plase need ur help.
Thanks

hi
then check in OVLP whether u have checked box for u r item category
and also check the document flow it might have already picked

Creation outbound delivery based on subcontracting purchase order

Dear experts,
I have the following flow: I'm creating a subcontracting order with a number of component in a BOM. I need an outbound delivery for each subcontracting order (and I'm likely to have multiple subcontracting orders per vendor per day), with a link in the delivery of both the FG (to be produced by the subcontractor) or at least the subcontracting PO. I've already looked at the ME2O transaction but this one seems to consolidate everything to one delivery per vendor, without a link to the PO.
An aditional requirement is that we need to be able to do a mass-creation of the deliveries,
Thanks in advance,
M

the delivery of components to a subcontractor has no relation to a subcontract order in core SAP.
Such feature is only possible with the new AD_SUBCON enhancement if I am not mistaken

Credit Check is not working while creation of the delivery

Hi,
Credit check is not performing while creation of the delivery.
As per current settings, there is no credit check at SO level. Ideally, system should show an error message while creation of the delivery if credit limit of the customer is exceeds.
Below is the current OVA8 setting for Delivery group 02.
It was working fine till last week, but due to some unknown changes in customization or master data, same is not working now.
Could you please check below settings and suggest if any setting is wrong?

You talking about the reaction field D am talking about beside to reaction field that is status/Block(check) .
Status/Block(tick) is used to block the document.
Where as you reaction field is used to give the either warning or error message based input you are giving
A and C gives warning message and allow to save the document.
B and D gives error message and will not allow to proceed further
Please check this and try system will block the delivery.
thanks,
Srinu.
Message was edited by: Srinu S

Delivery Note to Subcontract creation error "Essential transfer parameters

Similar Messages

Maybe you are looking for