Delivery document text control.

Hi All,
Is there a way to assign a text ID to a particular delivery type (NLCC) without creating a new text procedure?
Essentially the situation is that I have created a couple of Text IDs and they are part of an existing Text Procedure so whatever delivery types have been assigned to that Text Procedure, the texts appear on those deliveries. I just want those texts to appear on a couple of delivery types only (without the need of creating a new text procedure). Is it only possible by using a routine or can I do a configuration change too?
Regards,
George

Thanks Shiva Ram. I am thinking of the routine too but is that the only way to go here or can we do config too?
Regards,
George

Similar Messages

Issue with copy control of Delivery document to Billing document

Hi All,
I am having some issue with copy control of Delivery document to Billing document.
I am having two line items in Delivery documetn, one is for item to be delivered to customer and other which is created due to batch determination.
Now , when I create billing document (VF01) with reference to this delivery document , I want only one line item (for the one which needs to be delivered to customer).
I have used following things in copy contro from ZLF to ZF2:
Copying requirements: 004 ( Deliv-related item)
Data VBRK/VBRP: 007 "(Inv.Split (Rec/Div))
Is it correct or shall I use something else, so I have only one line item in Billing document.
Regards
Nidhi

Pls. search the forum.
Pls. refer the below link -
Line with 0 quantity for main item with batch split
Thanks

Shipping Instructions text not copied from Sales Order to Delivery Document

Hi All,
The Shipping instructions text in the Sales order Header is entered manually. Now when the delivery is created, the text is not getting copied to the Header text (shipping instruction note) of the Delivery document.
What may be the problem. Can anybody help ?

Hi
Check this link
http://learnsaptips.blogspot.com/2010/09/text-type-configuration-in-sap.html
regards
Prashanth

Customer texts to delivery document item level

Hello friends,
My requirement is for some customers I maintain load number in customer master texts field, for some customers I am not going to maintain.When I am creating delivery document if that load number is not triggered at item level, I should get a warning message.( that load number is not maintained)
By using text determination and log of incompleteness, How can I achieve this?Can we do it in standard?
Somebody can please advice me in this regard.
regards,
seetaram

In ECC 6 i have done, but not in delivery document, in sales order level if the Text data is not filled in CMR, sales order will not allow to save
After assigning the CMR Text ids to access sequences
Maintain this Access Sequence in the SD Text IDu2019s in Text procedure
here maintain the "text is obligatory "
if u likes these inputs pls points

Delivery document header text

Hi Guys,
Which table we can find the delivery document header text detatils?, Can any one please suggest.
Text object should be VBBK.
Thanks in advance.

you can find the details from STXH (header information )and STXL - Text information(non readable format)
using READ_TEXT you can find the information.
TDNAME = DELIVERYNUMBER(likp-vbeln)
TDOBJECT = VBBK for header VBBP for Item
TDID depends on the text which you are using.
you can get all the information from Text editior itself in the Delivery.

Sales header text to be copied to Delivery document(DelThrough the Project)

Hi,
We are creating sales order, which inturn creates Project in the system (Project System is integrated with Sales).
For creating the delivery usually we use VL01n but
We are creating a delivery document through transaction CNS0 since this delivery comes from Project.
Now the issue:
When we create the original Sales order, we maintain Shipping Instructions in sales order Header data.
Now,
when we are creating the delivery process like picking, Packing through VL02n (based on the document number created by CNS0) , we want the text entered in shipping Instructions in Sales order to be copied automatically to delivery header text, "Shipping Instructions". .
Please let us know if someone has faced such an issue and has a solution.

Hi Narendra,
Transaction code for this is VTLA. In this we can have our own requirements to copy the required information.
We can do this at the header level and also at the item category level also.
Thanks
Lakshman

Authorization Control for Delivery Document Deletion

Hi experts,
I know there's way to control the deletion of Sales Document through V_VBAK_AAT and V_VBAK_VKO.
However, how can I control the deletion of Delivery Document (in t-code VL02N)?
Thanks in advance.
Chin

Hi,
if you can't find a standard authorization object using standard tools such as SU24 and ST01 then there is a BADI LE_SHP_DELIVERY_PROC with method CHANGE_FCODE_ATTRIBUTES. This method is called whenever screen is displayed and can be used to exclude menu items e.g. Delete Delivery. So you can create a custom authorization object which will be used to control access to delete function.
Cheers

What controls the color of the cursor that selects text when you use the "Edit Document Text" tool?

Hi, I have had a student ask me a question I cannot answer: what controls the color of the cursor that selects text when you use the "Edit Document Text" tool?
I have only seen it appear as a black semicircle over each letter, but at a different computer in our training facility, this same tool appears as an aqua-green highlight.
Is it a preference I never noticed? Thanks for any info.

What version of Acrobat? What operating system?

STO Partner Copy Control to Outbound Delivery Document (NL)

Hi -
Partner Schema CR for 0003 UB Type has been maintained in configuration, which allows CR (Freight Forwarder) partner function to be manually added to UB Document Types (Partner Determination Process u2013 0003 Stock Transfr PurOrd).
However, even with this configuration the CR partner does not copy to the Outbound Delivery Document.
After some analysis, I found the following:
In program SAPLMEPO (MM06EF0P_PARTNERS) FORM PARTNERS in line 97 u201Ccheck EKKO-BSAKZ equal to spaceu201D; if purchase orders have EKKO-BSAKZ = 'T' then never determine partners. I have checked the EKKO table for field BSAKZ and all STOu2019s have a T in that field. If the code is looking for <blank> in order to apply the partner it looks like the program will not attempt to retrieve the Partner Functions with BSAKZ = T.
All other partners are getting copied to the outbound Delivery, such as PI (Invoicing Party), DP (Delivering Plant), SH (Ship-To)etc.
Is there a way to have Freight Forwarder partner copy control to Outbound Delivery document at time of Delivery create from either Vendor Master or Customer Master for STO (UB Purchase Order type) / Delivery type NL?
Thank you,
Karen

remark: for me the check is in line 113 (SAPKH60407).
Please read OSS note 842829:
2. The system does not transfer the partner data from the STO to the replenishment delivery. This particularly applies to the forwarding agent. The replenishment delivery uses only the customer of the receiving plant (EKPO-WERKS) as a partner. In the replenishment delivery, this customer (EKPV-KUNNR) is the direct goods recipient. The customer is not the sold-to party or a general debtor, for whom the system would determine a (different) goods recipient using the customer master in the replenishment delivery. If the PO header contains a vendor, you can use a modification to transfer the vendor as a partner to the replenishment delivery, if required. However, this is not the standard system behavior. There is no known modification for transferring the forwarding agent.

How to control the status of EDI message in delivery document

Hello:
We use user exit:EXIT_SAPLV56K_001 in function:IDOC_OUTPUT_Delivery to block the IDOC generation if delivery is blocked in GTS system.The IDOC generation can be blocked successfully by this user exit but the EDI message type will still have the status of "successfully processed" in the delivery doucment after IDOC generation is prevented.So user have to manually repeat the EDI Message type so that this EDI message type can be retriggerred by the background job of RSNAST00.
I am wondering if the EDI message in the delivery document can have the status of "not processed" even after IDOC generation is prevented.
BR
Thanks

Did you raise any exception like ERROR_MESSAGE_RECEIVED from the exit when the delivery is blocked?
The most important is the RSNASTED should get some exception to set RC = 4 (Non-zero). Only in that case, the EDI message type will go to error (i.e. VSTAT = 2) otherwise, by-default the RC = 0 unless we lead it to set to non-zero. Unless u make VSTAT = 2, you can't process it thru' RSNAST00 or better RSNAST0F for reprocessing the messages that go to error.

Output types for delivery documents

Hi All,
Please help me out.
Thanks in advance,
Here i got a requirement like i already have the output types for the delivery documents.However i need to copy the existed output types into different names bcoz to customize it for different organization in different region.
The problem is i already copied the o/p types but when i went to vl03n and tris to see the output , am not able to find my o/p type there...am i need to do anything more..
Please help me out as i am a ABAPER and not the functional guy am facing lot of difficulty...
again thanks in advance.

dear govardhan
please refer below
Output Determination Procedure
Output is a form of media from business to one of its business partners. The output can be sent to any of the partners defined in the document. Outputs are usually in the form of Order Confirmations, Freight List, Delivery Notes, Invoices & Shipping Notifications. Determining form of output is output determination
Types of Output: Print Output, Fax, Telex, E-Mail & EDI (Electronic Data Interchange)
PRINT OUTPUT:
SPRO- IMG- Basic Functions- Output Control- Output Determination- Output Det using Cond Tech- Output Det for Sales Documents & output determination for billing documents.
Create Condition Table: select the field Sales Doc Type from field catalog & Save
Maintain Access Sequence: 4-digits code & description. Assign condition table to access sequence. Select Accesses line item and Goto Fields. Fields will display the fields we have selected in the condition table i.e. sales doc type.
Select BA00 & Copy & Rename. Give the same 4-digit code as given to acc seq.
You Can Maintain:
Languages of Output
Partners (to whom we want to send output)
Print Program- print specification
Sap Script- layout
Assign Output Types to Partner Functions: go to new entries & assign your output type to partner functions.
Maintain Output Determination Procedure: V10000 (Standard Procedure). Go to new entries & create your own 6-digit code with descp. Select the procedure & go to Control Data. Here mention the output type i.e. cond type & leave requirement and manual only columns as blank.
Determination Rule: link the 6-digit procedure code to doc types.
Create Condition Records: VV11. Select document type and click on Communication. Mention partner function, medium, time. Output device: LP01, Spool request Name: SD_003, Suffix 2: order_confir & flag on print immediately.
Once you press enter you will come across 2 key combinations:
Sales organization/ Customer Number: fill SO, Customer No, Partner Function Abbreviation, Partner to whom the output should be sent, time, medium, language. {It contains: Sales Orgn, Customer, Partner Function (The abbreviated form of the name that identifies the Partner) (During output determination, the system determines the recipient of the output from the master record for the specified partner function. In this field, you can explicitly specify a recipient that will override the standard partner. There must also be a master record for the partner that is specified explicitly.), Medium, Time & Language.}
Order Type: Document Type, Partner Function (abbreviation), Partner, Medium, Time & Language.
In SAP we can send the documents to respective partner functions through different transmission mediums. SAP uses condition technique to determine output t relevant partners with relevant transmission mediums.
Out put determination procedure has a integration with technical module, as ABAPers has to write SMART forms and FORMS to print the output , that SMART form output can be send to relevant partner function through relevant transmission mediums.
Out put determination procedure for order confirmation: (V/57)
a) Maintain condition table:
Path:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain condition tables
Maintain out put condition table for sales document
Here we define condition table
Ex: 007 order type (sales order types)
Save it
b) Maintain output types:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain out put types
Here we define out put types
Ex:     AF00 -- Inquiry
     AN00 quotation
     BA00 Order confirmation
     BA01 EDI odd response
     KRMLCredit processing
     LP00 -- Scheduling agreement
     MAIL Internal message
     RD03cash sales invoice
Choose BA00 copy it and rename as a MA00
click on details icon
click on display to change icon
then again choose MA00 click on details icon
Maintain data in general data tab
General data tab:
Access sequence: 0010(order type)
In IMG define access sequence and assign to the output type
Check access to conditions:
     This indicator allows the system to read the condition records for output. If it is not been activated then system determines out put from customer master ex: By following out put determination procedure DB0001
Check cannot be changed:
     This control specifies whether the out put can be changed or not
Ex: direct mailings can be changed during processing
Check multiple issuing:
This indicator allows the system to send the output multiply
Ex: sales order has been sent for 10 items again one item has been added to sales order so that business has to issue the new out put for sold to party with added line items. This indicator allows the system to send out put repeatedly.
Check partner independent out put:
During output processing when the indicator has not set then system allows only specific functions in specific partner functions
Dont write processing:
This indicator determines whether system has to write processing log for output
Default values tab:
Dispatch time:
Ex: send immediately: when carry the application this indicator determines when the output should be sent.
Transmission medium:
Ex:     print out
     Fax
     Telex
     Internal send
     EDI
     Simple mail
     Special function
     Events (SAP business workflow)
     Distribution (ALE)
     Tasks (SAP business work flow)
Specify the transmission medium through which the output should be sent. (Ex: print output)
Communication strategy
Specify the communication strategy if you want to send the output externally
A) Time tab:
Check timing: (Periodic job not allowed)
This indicator allows the system to carry out print program periodically.
B) PRINT NEXT TAB):
Print parameter: Ex sales org.
     Specify the print parameter.
Click on mail title & Text control button under dialog structure.
Here we assign title for the mail along with relevant text Ex:-EN (English)
Processing routines control button under dialog structure.
Here we assign programs form routines & form that are written by ABAPER, they           they various transmission mediums.
Ex; - Transmission medium      shortest      program     form routine
          1                  print out     RVADOR       entry
Click on position function control button here we assign relevant partner function to relevant transmission mediums
          EX: print out: SP (Sold to party)
C) Maintain access sequences:
     Here we define Access sequence.
EX: 0010 & Assign the condition tables to this output.
D) Assign out put types to partner function:
     Here we assign output types along with transmission mediums to relevant partner functions.
EX:      Out put type          Transmission medium
       MA00                    1
                              2
                              6
                              A
       MAIL                    7
E) Maintain output determination procedure:
     Here we define output determination procedure
Ex:     V10000     -     Order output
     V05000     -     Inquiry output
     V06000     -     quotation output
     V10001     -     Cash sales output
Choose output determination procedure EX; V10000, copy it& rename it as MA0000
Assign output type MA00 by going control date section.
Save it.
F) Assign output determination procedures;
Allocate sales document Header.
_ Choose sales document type OR & Assign output determination procedure i.e MA0000 & Assign output type MA00.
Assign sales document items.
-Choose item category TAN & Assign output determination procedure Ex: Ma0000
- save it & exit.
Maintain output records (vv11)
Path:
Logistic > S&D > Master data > output > sales document > VV11 Create
Specify output MA00, Click on Key combination & specify sales document type (OR), partner function (sp) transmission medium (1) dispatch type (4) language (EN)
Click on communication button on application tool bar
Specify output device LOCL or LP01
Check print immediately check release after output
Save it
Go to Va01 raise the sales order
Go to extra button output header edit.
Specify output type: MA00 partner function
Select line, click on communication methods
Specify logical destination
Check print immediately
Check release after output
go back save it & exit
Go to VA02, Go to Extras output header print preview
Check out (order confirmation
(ERROR: out put MA00 for partner cannot be processed)
rewards pls
siva

Unable to capture condition type in delivery document

There are deliveries in production server, for the same destination zone, in which, for some deliveries, the condition Z52L is not determined and for some other deliveries, the condition Z52L is determined although the condition record for its plant with its corresponding destination zone is maintained in VK13.
For example, if we take 2 documents with the same Ship-To-Party, same Plant, and same Destination Zone:
1 delivery document, condition Z52L is properly determined while the other
delivery document, condition Z52L is not determined.
Another good representative example if we take 2 delivery documents with the same Ship-To-Party, same Plant and same destination zone:
1 delivery document, condition Z52L is properly determined while the other
delivery document, condition Z52L is not determined.
But in the analysis pricing of the delivery document, there is no destination zone found but still it captures the condition Z52L by just referring to the transportation zone of the ship to party while the other delivery document cannot able to capture it since there is no maintained condition record for those with blank destination zone in VK13.
Another point that we want to clarify is even the user update the pricing in the delivery document, still the condition was not yet updated even it is already maintained in VK13.
Please help and explain this issue to us.
Thank you in advance. Hoping for your assistance on this matter.
Reyna Agustin

hi,
for the first errot check if you have maintained the item level copy control (from sales order to del). if yes check the settings against the field 'pos/- qty'. put a + here. for the second issue check in the item level copy ctrl from sales order to billing maintain 'd' in the price type.
saurabh

Item number in billing document not matching with delivery document-reg

Hi All,
In the billing document the item number is coming from Shipment document. ie., there are three deliveries in a shipment. Each delivery has got one line item, ie., 10. These three deliveries are assigned to a shipment, the order in which the deliveries are attached if we take as 10 for first delivery, 20 for th esecond and 30 for the third, In billing document the billing from first delivery is getting the item number as 10, the second delivery's billing document is getting the item number as 20 and the third as 30.
Can someone please reply where and how this is configured?
Thanks and regards,
Tajudeen S.

Hi,
first look at IMG/Sales and Distribution/ Billing / Maintain Copying Control For Billing Documents / Copying control: Delivery document to billing document
There is a field "Copy item number from reference"
Maybe it helps.
regards
Wojciech

How 2 creat report for displaying the details of a Delivery Document using

how to create report for displaying the details of a Delivery Document using the tables LIKP, LIPS
thank you
regards,
jagrut bharatkumar shukla
points will be rewarded

HI
I AM GIVING YOU MY DELIVERY DOCUMENT CODE...MODIFY IT ACCORDING TO YOUR REQUIREMENT
*& Report ZDELIVERY                                *
report zdelivery message-id z9bhu          .
types: begin of t_likp,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
*           LFDAT TYPE LIKP-LFDAT,      "Delevery Date
*           WAERK TYPE LIKP-WAERK,      "Currency
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
       end of t_likp.
types: begin of t_lips,
           vbeln type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,
*           MEINS TYPE LIPS-MEINS,      "Base Unit of Measure
           vgbel type lips-vgbel,      "Doc no of the reference document
        end of t_lips.
types: begin of t_vbpa,
           vbeln type vbpa-vbeln,      "SD DocumenT Number
           posnr type vbpa-posnr,      "Item number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,      "Customer Number 1
       end of t_vbpa.
types: begin of t_kna1,
           kunnr type kna1-kunnr,      "Customer Number 1
           name1 type kna1-name1,      "Name 1
           ort01 type kna1-ort01,      "City
           adrnr type kna1-adrnr,      "Address
       end of t_kna1.
types: begin of t_li_vbpa,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
*           LFDAT TYPE LIKP-LFDAT,      "Delevery Date
*           WAERK TYPE LIKP-WAERK,      "Currency
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
           vbeln1 type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,      "Net Price
*           MEINS TYPE LIPS-MEINS,      "Base Unit of Measure
           vgbel type lips-vgbel,      "Doc no of the reference document
           vbeln3 type vbpa-vbeln,     "SD DocumenT Number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,      "Customer Number 1
       end of t_li_vbpa.
types: begin of t_final,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
           vbeln1 type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,      "Net Price
           vgbel type lips-vgbel,      "Doc no of the reference document
           vbeln3 type vbpa-vbeln,     "SD DocumenT Number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,     "Customer Number 1
           name1 type kna1-name1,      "Name 1
           ort01 type kna1-ort01,      "City
           adrnr1 type kna1-adrnr,     "Address
           name2 type kna1-name1,      "Name 1
           ort02 type kna1-ort01,      "City
           adrnr2 type kna1-adrnr,     "Address
           name3 type kna1-name1,      "Name 1
           ort03 type kna1-ort01,      "City
           adrnr3 type kna1-adrnr,     "Address
       end of t_final.
*            D A T A D E C L A R A T I O N
*&*********Internal Table Declaration****************&*
data: it_likp type standard table of t_likp.
data: it_lips type standard table of t_lips.
data: it_vbpa type standard table of t_vbpa.
data: it_kna1 type standard table of t_kna1.
data: it_li_vbpa type standard table of t_li_vbpa.
data: it_li_vbpa_temp type standard table of t_li_vbpa.
data: it_final type standard table of t_final.
*&*********Work Area Declaration********************&*
data: wa_likp type t_likp.
data: wa_lips type t_lips.
data: wa_vbpa type t_vbpa.
data: wa_kna1 type t_kna1.
data: wa_li_vbpa type t_li_vbpa.
data: wa_li_vbpa_temp type t_li_vbpa.
data: wa_final type t_final.
*&*********Data Declaration************************&*
data: d_vbeln type likp-vbeln.
data: flag type i value 0.
*           S E L E C T I O N S C R E E N   D E C L A R A T I O N
selection-screen begin of block block2 with frame title text-001.
select-options: s_vbeln for d_vbeln obligatory.    "Delivery no
selection-screen end of block block2.
*            A T S E L E C T I O N - S C R E E N   E V E N T S
*AT SELECTION-SCREEN.
*PERFORM VALIDATE_DATA.
*            S T A R T   O F S E L E C T I O N     E V E N T S
start-of-selection.
perform fetch_data.
perform merge_data_kna1.
*INCLUDE Z9BT_SH_***4_FORMS.
call function 'OPEN_FORM'
exporting
*   APPLICATION                       = 'TX'
*   ARCHIVE_INDEX                     =
*   ARCHIVE_PARAMS                    =
    device                            = 'PRINTER'
*   DIALOG                            = 'X'
*   FORM                              = ' '
   language                          = sy-langu
*   OPTIONS                           =
*   MAIL_SENDER                       =
*   MAIL_RECIPIENT                    =
*   MAIL_APPL_OBJECT                  =
*   RAW_DATA_INTERFACE                = '*'
*   SPONUMIV                          =
* IMPORTING
*   LANGUAGE                          =
*   NEW_ARCHIVE_PARAMS                =
*   RESULT                            =
exceptions
   canceled                          = 1
   device                            = 2
   form                              = 3
   options                           = 4
   unclosed                          = 5
   mail_options                      = 6
   archive_error                     = 7
   invalid_fax_number                = 8
   more_params_needed_in_batch       = 9
   spool_error                       = 10
   codepage                          = 11
   others                            = 12
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
sort it_final by vbeln.
loop at it_final into wa_final.
call function 'START_FORM'
exporting
*   ARCHIVE_INDEX          =
   form                   = 'Z9BT_DELIVERY'
   language               = sy-langu
*   STARTPAGE              = ' '
*   PROGRAM                = ' '
*   MAIL_APPL_OBJECT       =
* IMPORTING
*   LANGUAGE               =
exceptions
   form                   = 1
   format                 = 2
   unended                = 3
   unopened               = 4
   unused                 = 5
   spool_error            = 6
   codepage               = 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.
call function 'WRITE_FORM'
exporting
   element                        = 'ITEM_LIST'
   function                       = 'SET'
   type                           = 'BODY'
   window                         = 'MAIN'
* IMPORTING
*   PENDING_LINES                  =
* EXCEPTIONS
*   ELEMENT                        = 1
*   FUNCTION                       = 2
*   TYPE                           = 3
*   UNOPENED                       = 4
*   UNSTARTED                      = 5
*   WINDOW                         = 6
*   BAD_PAGEFORMAT_FOR_PRINT       = 7
*   SPOOL_ERROR                    = 8
*   CODEPAGE                       = 9
*   OTHERS                         = 10
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function 'END_FORM'
* IMPORTING
*   RESULT                         =
exceptions
   unopened                       = 1
   bad_pageformat_for_print       = 2
   spool_error                    = 3
   codepage                       = 4
   others                         = 5
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endloop.
call function 'CLOSE_FORM'
* IMPORTING
*   RESULT                         =
*   RDI_RESULT                     =
* TABLES
*   OTFDATA                        =
exceptions
   unopened                       = 1
   bad_pageformat_for_print       = 2
   send_error                     = 3
   spool_error                    = 4
   codepage                       = 5
   others                         = 6
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
*&      Form VALIDATE_DATA
*       text
* --> p1        text
* <-- p2        text
form validate_data .
select single vbeln into wa_likp-vbeln
                    from likp where vbeln in s_vbeln.
append wa_likp to it_likp.
if sy-subrc <> 0.
flag = 1.
endif.
endform.                    " VALIDATE_DATA
*&      Form FETCH_DATA
*       text
* --> p1        text
* <-- p2        text
form fetch_data .
select a~vbeln
       a~erdat
       a~kunnr
       a~kunag
       a~traty
       b~vbeln
       b~posnr
       b~matnr
       b~arktx
       b~lfimg
       b~netpr
       b~vgbel
       c~vbeln
       c~parvw
       c~kunnr
         into table it_li_vbpa
                from likp as a
                left outer join lips as b on a~vbeln = b~vbeln
                inner join vbpa as c on b~vgbel = c~vbeln
                where a~vbeln in s_vbeln and
                c~parvw = 'RE'.
endform.                    " FETCH_DATA
*&      Form MERGE_DATA_KNA1
*       text
* --> p1        text
* <-- p2        text
form merge_data_kna1 .
if it_li_vbpa[] is not initial.
it_li_vbpa_temp[] = it_li_vbpa[].
sort it_li_vbpa_temp by kunnr.
delete adjacent duplicates from it_li_vbpa_temp comparing kunnr.
loop at it_li_vbpa into wa_li_vbpa.
read table it_li_vbpa_temp into wa_li_vbpa_temp with key kunnr =
wa_li_vbpa-kunag.
if sy-subrc <> 0.
wa_li_vbpa_temp = wa_li_vbpa.
append wa_li_vbpa_temp to it_li_vbpa_temp.
endif.
read table it_li_vbpa_temp into wa_li_vbpa_temp with key kunnr =
wa_li_vbpa-kunnrb.
if sy-subrc <> 0.
wa_li_vbpa_temp = wa_li_vbpa.
append wa_li_vbpa_temp to it_li_vbpa_temp.
endif.
endloop.
endif.
if it_li_vbpa_temp[] is not initial.
select kunnr
        name1
        ort01
        adrnr into table it_kna1 from kna1
                    for all entries in it_li_vbpa_temp
                    where kunnr = it_li_vbpa_temp-kunnr.
endif.
loop at it_li_vbpa into wa_li_vbpa .
wa_final-vbeln = wa_li_vbpa-vbeln.
wa_final-erdat = wa_li_vbpa-erdat.
*it_final-LFART = it_li_vbpa-LFART.
wa_final-kunnr = wa_li_vbpa-kunnr.
wa_final-kunag = wa_li_vbpa-kunag.
*it_final-VSTEL = it_li_vbpa-VSTEL.
wa_final-traty = wa_li_vbpa-traty.
wa_final-vbeln1 = wa_li_vbpa-vbeln.
wa_final-posnr = wa_li_vbpa-posnr.
wa_final-matnr = wa_li_vbpa-matnr.
wa_final-arktx = wa_li_vbpa-arktx.
wa_final-lfimg = wa_li_vbpa-lfimg.
wa_final-netpr = wa_li_vbpa-netpr.
*wa_final-GEWEI = it_li_vbpa-GEWEI.
*it_final-VOLUM = it_li_vbpa-VOLUM.
*it_final-VOLEH = it_li_vbpa-VOLEH.
wa_final-vgbel = wa_li_vbpa-vgbel.
wa_final-vbeln3 = wa_li_vbpa-vbeln.
*wa_final-PARVW = wa_li_vbpa-PARVW.
wa_final-kunnrb = wa_li_vbpa-kunnrb.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunnr.
if sy-subrc = 0.
wa_final-name1 = wa_kna1-name1.
wa_final-ort01 = wa_kna1-ort01.
wa_final-adrnr1 = wa_kna1-adrnr.
endif.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunag.
if sy-subrc = 0.
wa_final-name2 = wa_kna1-name1.
wa_final-ort02 = wa_kna1-ort01.
wa_final-adrnr2 = wa_kna1-adrnr.
endif.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunnrb.
if sy-subrc = 0.
wa_final-name3 = wa_kna1-name1.
wa_final-ort03 = wa_kna1-ort01.
wa_final-adrnr3 = wa_kna1-adrnr.
endif.
append wa_final to it_final.
clear wa_final.
endloop.
endform.

Delivery document - sales order - no stock items

Hello,
when we create a delivery document out of a sales order, we face the problem that certain material items in the sales order with no stock will be copied to the delivery document. Other materials that have no stock will not be copied into the delivery document.
Where in SAP can I do the customizing for that situation?
Thanks
Anne

> when we create a delivery document out of a sales order, we face the problem that certain material items in the sales order with no stock will be copied to the delivery document. Other materials that have no stock will not be copied into the delivery document.
> Where in SAP can I do the customizing for that situation?
Generally when Availability check is active system should not copy the Material which are not available. I can think this may be because of following reason
1.. Check your configuration of the Item Category using 0VLP. There is stock determination rule fields, i dont have access to SAP so not sure but please check whether there is any setting.
2. check in copy control VTLA for the item category whether you have maintained the following:-
Order requirements-->101
Item data-->101
Update document flow-->X
Pos./neg.quantity-->+
And if these seems ok, Then you have to check the routines in the copy controls.
Thanks,
Raja

Delivery document text control.

Similar Messages

Maybe you are looking for