Creation of TO Automatically for Delivery

Hi All
Our Storage type is SU Managed Bulk Storage Type , accordingly we have maintained in material master WM2 different storage unit types,also set up indicators in WM1 for removal and palcement strategies.
Now our requirement is as below...
1. TO creation for delivery - TO is not confirmed automatically ,when we try to confirm manually either forground or
    background,sytem prompts to enter storage unit number manually.
    We would like this to be automated ie the storage unit number should be picked up automatically by the system during TO
   creation and also TO should be confirmed and created.
2.Can we automate creation of TO at the time doing PGI.
3.We would also like to print the TO automatically after PGI.
Thanks in advance
Samson

Hi
For Delivery
Go to LE - WM - Interfaces - Inventory Management - Activate Automatic TO Creation - Movement types - Assign
Here for your WH No select the movement type 601 and delselect TR creation & Immed.TO creation
For Goods Receipt
Go to LE - WM - Activities - Transfers - Set Up Autom. TO Creation for TRs / Posting Change Notices
Automatic TO creation - Control data here for the secon WH No where you do not want auto TO remove the
tick mark
Also make relevant changes in in the next - Movements - assign control select the WH no and the movement
no and check for auto TO setings.
Regards
Samson

Similar Messages

Block the Material at Item level in Sales Order automatically for delivery

Hi!
My business scenario needs a material to be Ckecked for Inspection after raising the Sales Order by thirdparty person. So, I need to block that particular material at Item level automatically for delivery and rest of the line items can get delivered. I can do this by selecting the reason for Block at Item level manually, but I want the system to get detemine this block. And one more thing is that there is NO Quality Management module for this. So, let me know what I need to configure for this effect. Thank you.....

hi,
pl check the user exit " userexit_save_document_prepare" or "userexit_save_document".
Take the help of your abaper to see if the logic written here can affect the item level block in the sales order for inspection. Create new reason for the item level block and have it triggered with this exit. Instead of hard coding which might require regular intervention of abaper for code changes for the business to be able to manage it, maintain a master data in the material master against some field with a key.
now use that key to identify if these materials require to be blocked at the sales order level for inspection. To release this item again the user has to go in VA02 mode to release the block. Let this be done after the inspection of that material.
regards
sadhu kishore

Creation of New Table for Delivery Output Type.

Hi Guys,
I need to replace an existing table by creating a new Table in the existing Access Sequence with the combination of "Ship to Party/Product Hierarchy".
Logistics>Shipping>basic Shipping functions>Output determination>Maintain Condition Tables-->maintain output condition table for deliveries.
I am choosing a new table by the name 902, but i am not getting the field " PRODH Product Hierarchy" on the right hand side to choose from.
I checked the field catelog also. Firstly the field catelog was also not having the field, and then i added the field in it by choosing new entries.
I guess i am missing some step in between, thats why the new field (PRODH) is not showing on the right hand side while creation of the condition table.
One more thing, when i am seeing the Field Catelog, i am able to see a very large number of fields, then why only a few are appearing during creation of a new table??????
Can you guys correct me and let me find a way.????
Thanks very much indeed.
Regards,
Vivek

Hi If u have already the field in FC u can add with new entries .
Try with ,enter t- code SE11, enter KOMB- it will ask for access key get from basis and add u r Field catalog
Field catalog for condition key: output determination
If at all u want a new field tao add to u r FC u Can try with userexit.
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields.
 The fields which are not in either of the two tables KOMK and KOMP
cannot be used in pricing .Sometimes a need arises when the pricing
is to be based on some other criteria which is not present in the form of fields in either of the two tables.
This problem can be solved by using USEREXITS which are provided for pricing in SD.
Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP
program SAPMV45A. The name of the userexits are same. i.e
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely
created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that
has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose
includes are provided in each of them .
To create the field in header data(KOMK) the include provided is KOMKAZ
and to create the field in item data(KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2)The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
Message was edited by:
 SHESAGIRI GEDILA

User-exit for delivery while assigning serial numbers(urgent)

hi all,
can u plz tell me the specific user exit for delivery (VL01n) while assigning serial numbers?
i am getting the serial numbers for material in database table OBJK .i am also getting these serial no.s in IQ01.
   while doing delivery,i am going for extra-->serial number.at this time one screen for serial number is comming.those serial numbers which are stored in objk will transfer to this screen of delivery automatically.
for this , i want a specific user-exit for delivery so that i can transfer the serial nos from objk to that screen of delivery.plz suggest .(urgent )
any idea is highly appreaciated
Regards
pabitra

You can find from below list of user exists
V02V0001            Sales area determination for stock transport order
V02V0002            User exit for storage location determination
V02V0003            User exit for gate + matl staging area determination (headr)
V02V0004            User Exit for Staging Area Determination (Item)
V50PSTAT            Delivery: Item Status Calculation
V50Q0001            Delivery Monitor: User Exits for Filling Display Fields
V50R0001            Collective processing for delivery creation
V50R0002            Collective processing for delivery creation
V50R0004            Calculation of Stock for POs for Shipping Due Date List
V50S0001            User Exits for Delivery Processing
V53C0001            Rough workload calculation in time per item
V53C0002            W&S: RWE enhancement - shipping material type/time slot
V53W0001            User exits for creating picking waves
VMDE0001            Shipping Interface: Error Handling - Inbound IDoc
VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)

Extended Idoc - User exit for delivery VL01 and Invoice VF01

Hi Experts,
We are developing Extended Idoc for order - cash cycle.The extended Idoc contains 4 extra fields.
I want to know the User exits where i can populate the extended segment field values for VL01 and VF01 transactions.

HI
exits available for VL01.
VMDE0004                                Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003                                Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002                                Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001                                Shipping Interface: Error Handling - Inbound IDoc
V53W0001                                User exits for creating picking waves
V53C0002                                W&S: RWE enhancement - shipping material type/time slot
V53C0001                                Rough workload calculation in time per item
V50S0001                                User Exits for Delivery Processing
V50R0004                                Calculation of Stock for POs for Shipping Due Date List
V50R0002                                Collective processing for delivery creation
V50R0001                                Collective processing for delivery creation
V50Q0001                                Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT                                Delivery: Item Status Calculation
V02V0004                                User Exit for Staging Area Determination (Item)
V02V0003                                User exit for gate + matl staging area determination (headr)
V02V0002                                User exit for storage location determination
V02V0001                                Sales area determination for stock transport order
For VF01..
Enhancement
V61A0001                                Customer enhancement: Pricing
V60P0001                                Data provision for additional fields for display in lists
V60A0001                                Customer functions in the billing document
V05N0001                                User Exits for Printing Billing Docs. using POR Procedure
V05I0001                                User exits for billing index
SDVFX011                                Userexit for the komkcv- and kompcv-structures
SDVFX010                                User exit item table for the customer lines
SDVFX009                                Billing doc. processing KIDONO (payment reference number)
SDVFX008                                User exit: Processing of transfer structures SD-FI
SDVFX007                                User exit: Billing plan during transfer to Accounting
SDVFX006                                User exit tax line in transfer to accounting
SDVFX005                                User exit reserves in transfer to accounting
SDVFX004                                User exit G/L line in transfer to accounting
SDVFX003                                User exit cash clearing in transfer to accounting
SDVFX002                                User exit for A/R line in transfer to accounting
SDVFX001                                User exit header line in delivery to accounting
J_3RSINV

User exit for Delivery output execution

Hello All,
 My query is i need a delivery relevant user exit for output trigger which the specific order reason and for this only it should trigger in the VL01N (delivery) output. Kindly let me know if any user exit is there where i can give my condition(by checking the specific order reason from the proceding sales document) and for that only it should trigger in the VL01N output . PLZ let me know the answer ASAP.

Hi
Check the following enhancements and BADI's
Enhancement
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
V53W0001 User exits for creating picking waves
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53C0001 Rough workload calculation in time per item
V50S0001 User Exits for Delivery Processing
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V50R0002 Collective processing for delivery creation
V50R0001 Collective processing for delivery creation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT Delivery: Item Status Calculation
V02V0004 User Exit for Staging Area Determination (Item)
V02V0003 User exit for gate + matl staging area determination (headr
V02V0002 User exit for storage location determination
V02V0001 Sales area determination for stock transport order
Business Add-in
DELIVERY_ADDR_SAP Address Change in Delivery Processing
DELIVERY_PUBLISH Announcement of delivery data during database update
Also look at the Standard program of Delivery SAPMV50A
for the user exit Include MV50AFZZ
Reward points for useful Answers
Regards
Anji

User Exit for Delivery Updating

Hi,
I am creating one user exit for delivery ,
My condition:
If XLIKP-UPDKZ (Update indicator) = Update (U).
Read table Deferred COGS Activity (Z1009) with key
Delivery Number eq LIKP-VBELN.
If sy-subrc <> 0
Exit.
Else.
If V50AGL-WARENAUSGANG=X (PGI is active)
Update table Z1009 with
WADAT_IST = XLIKP-WADAT_IST
PGI_ERNAM = SY-UNAME
PGI_ERDAT = SY-DATUM.
where Delivery Number (DL_NO) eq LIKP-VBELN.
If delivery updated successfully then no problem ,
if not updated then I need to through error message to log.
I need Function Module for this.
Can u help me.

These ar all the User Exits used in VL01N.
Exit Name Description
V02V0001 Sales area determination for stock transport order
V02V0002 User exit for storage location determination
V02V0003 User exit for gate + matl staging area determination (headr)
V02V0004 User Exit for Staging Area Determination (Item)
V50PSTAT Delivery: Item Status Calculation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50R0001 Collective processing for delivery creation
V50R0002 Collective processing for delivery creation
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V50S0001 User Exits for Delivery Processing
V53C0001 Rough workload calculation in time per item
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53W0001 User exits for creating picking waves
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
You can also look at BADI: LE_SHP_DELIVERY_PROC. It has several implementations which could be useful to you.

USER-EXIT for DELIVERY--very very urgent

Hi all,
can u plz tell me the user-exit for delivery i.e this exit should be called after the delivery order is created.
plz suggest some specific exit.it is very very urgent.
Regards
pabitra

Rout ,
u cannt find out user exits after the Creation.
V02V0001            Sales area determination for stock transport order
V02V0002            User exit for storage location determination
V02V0003            User exit for gate + matl staging area determination (headr)
V02V0004            User Exit for Staging Area Determination (Item)
V50PSTAT            Delivery: Item Status Calculation
V50Q0001            Delivery Monitor: User Exits for Filling Display Fields
V50R0001            Collective processing for delivery creation
V50R0002            Collective processing for delivery creation
V50R0004            Calculation of Stock for POs for Shipping Due Date List
V50S0001            User Exits for Delivery Processing
V53C0001            Rough workload calculation in time per item
V53C0002            W&S: RWE enhancement - shipping material type/time slot
V53W0001            User exits for creating picking waves
VMDE0001            Shipping Interface: Error Handling - Inbound IDoc
VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)
*        FORM-Routinen für Userexits
         include mv50afzz.
         include mv50afz1.
         include mv50afz2.
         include mv50afz3.          "Userexit neu zu Release 3.0A
         include mv50afzk.          "Userexit 4.6A (KOMKG/KOMPG)
         include mv50afzl.          "Userexit 4.6A Liefergruppen
                                                               "n_693000
         include mv50afzp.          "Userexit for pricing screen input
Regards
Prabhu

Automatic TO creation for delivery

Dear Experts ,
We are facing a problem with Automatic TO creation for delivery only in some storage types ( not all the types , some types are working fine )
The problem happened after we applied a user exit for a specific picking strategy , but even after we have cancelled that user exit still problem remained.
We have checked the following settings, and everything seems fine:
1-Warehouse management - Activities u2013 transfers u2013 define Mvt type
2-Warehouse management u2013 interfaces- Automatic TO creation
Looking for your help in this issue
Thanks ,
Malik

Hi Malik,
You mentioned that you have previously implemented the picking user-exit and removed it later. Did you enter the correct picking strategy for the effected storage types after removing the user-exit? This could be one reason.
What happens when you try to create the TO manually?
Regards,
Osman

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

Automatic creation of TO's for Handling Unit Inbound Delivery -del type HID

Hi Guru's,
I would like to create the putaway TO's for a Handling Unit inbound delivery automatically (delivery type HID). This means at the moment of the creation of the Inbound Delivery. The packing is also automatically done by the customizing of the delivery type. Did somebody faced this requirement before?
Thx,
Carl

I found the solution:
Choose Customizing activity Define Output Types for Inbound Delivery, and define output type WMTA. Enter the following values in the detail view of output type WMTA under General Data:
Enter an existing Access sequence. Access sequence 0001 is predefined in the standard system.
Set the indicator Access to conditions.
Set the indicator Partner-indep. output.
Save your entries.
In the menu tree, choose the entry Processing Routines in the Customizing activity Define Output Types, and enter the following values:
Choose entry 8 (special function) for the indicator Transmission Medium.
Enter RLAUTA20 in the field Program.
Enter ENTRY in the field Form Routine.
Save your entries.
Choose the Customizing activity Maintain Output Determination Procedure.
Define a procedure and enter the output type WMTA in the control view of the procedure. The procedure E10001 is predefined in the standard system.
To define a suitable condition record for inbound deliveries,
choose Logistics -> Materials Management -> Purchasing -> Master Data ->
Messages -> Inbound Delivery -> Create from the SAP menu.
Enter the output type WMTA.
Enter output medium 8 (special function) for delivery type Inbound Delivery.
Select the desired Date/Time.
Select the desired Language.
Cheers,
Carl

Automatic creation of Transfer order for Picking and putaway

Hello All .
I would appreciate if someone can explain the process of configuring Automatic creation of Transfer order for Picking ( outbound delivery)and putaway( inbound delivery) .
thanks
Rahul

Hi
To have transfer orders created automatically in the background, you must first set the indicator Automatic transfer order creation for each respective movement type in the Customizing application for Warehouse Management under the path Activities - Transfers - Define Movement Types. The system automatically copies this indicator into the header item of the source document.
For more information on how to set up automatic transfer order creation for transfer requirements and posting change notices, refer to the IMG for Warehouse Management under the path Activities - Transfers- Set up Autom. TO Creation for TR/Posting Change Notices.
You can find more details on this link
http://help.sap.com/saphelp_47x200/helpdata/en/c6/f85c504afa11d182b90000e829fbfe/frameset.htm
Thanks & Regards
Kishore

CRM - Automatic Return Delivery for Customer Owened Repair sales order

Hi Guys,
We are implementing Customer Owned Repair sales order Process in CRM and requirement is that once order gets replicated in ECC, automatic Return delivery should be created.
We have following settings done,
1. Order Type ZREP has automatic delivery creation set : A
2. Item category has special stock indicator E and and Returns
3. schedule line category IR has 653 Movement with special Stock E and availability is not flagged.
so in this configuration, when i create Order Manually, Return delivery gets created automatically even if there is Zeor stock (Schedule line confirms the Qty) but while Order gets replicated from CRM it does not because schedule line does not confirm the qty (Zero Qty).
Please advise on this asap as we are in verge of delivery and facing this issue.
Regards,
Dharmesh.

Hello Peter,
Regarding Posting of Goods Issue for Spare Parts in SAP R/3 Materials Management,
The data posted depends on the logistics scenario(s) that you use. The system therefore first determines the logistics scenario defined for the combination of transaction type, item category, service organization, and other relevant information required for the scenario (for example, movement type or special stock indicator in SAP R/3).
Availability information informs you whether the service parts are currently in stock. Each service part item generates a reservation in the back end system, which can be used to trigger an early procurement process.
To know more about the same refer the below link:
http://help.sap.com/search/highlightContent.jsp
http://help.sap.com/saphelp_crm50/helpdata/en/cb/f876d513c56e4e864c15517ff67e92/frameset.htm
Hope this helps!
Thanks and Best Regards,
Shanthala Kudva.

Sales order need to be blocked for delivery while creation

Hi experts,
                My requirement is to block sales orders for delivery, for the selected distribution channels, and for selected countries while creation itself, so for this I came to known that a program MV45AFZZ include, here in this at which form can I write code to block SO for delivery. and is it enough to put a reason in the field LIFSK in VBAK table to block SO for delivery.
Thanks in advance
Regards
SriNivas........

Hi,
You can use form routine USEREXIT_SAVE_DOCUMENT_PREAPRE of user exit MV45AFZZ to update the delivery block.
MOVE '10' to vbak-lifsk.                    "13 is the reason for block in header"
MOVE '10' to xvbak-lifsk.                  "13 is the reason for block in header"
Use following code to update delivery block at item level
MOVE '10' to vbep-lifsp.                      "13 is the reason for block in item schedule line"
MOVE '10' to xvbep-lifsp.                    "13 is the reason for block in item schedule line"
Regards
Vinod

What configuration is need for TO creation and confirmation automatically

Hi experts,
our business hope TO can be created and confirmed automatically in backgroup based on TR when GR, GI, how to configure it? Thank you.
Current system configuration:
1. every material have a fixed bin in master data.
2. Putaway strategy is fixed bin.
3. Pickup strategy is FIFO.

Hi Greetings
TO can be created and confirmed automatically
Immediate TO creation
OMLR --> Mark the field Indicator: Create transfer order immediately with A-Start transfer order creation in the background
for the Warehouse number and reference Movement type combination.
Immediate TO confirmation
SPRO --> Logistics Execution > Warehouse Management> Activities> Transfers> Define Movement Types --> In the details screen tick "TO item can be confirmed immediatly" check box.
Gobinathan G

Creation of TO Automatically for Delivery

Similar Messages

Maybe you are looking for