Transfer Order Collective Form
Hi All,
I am working on TO Collective form. This form has a delivery number in it. But my requirement is they need the last 3 digits of the Delivery Number to be printed in a bigger font beside the company logo.
I have written the following code in the subroutine.
FORM LAST_3 TABLES int_inval STRUCTURE itcsy int_outval STRUCTURE itcsy.
DATA: w_nlpla type ltap-nlpla.
Read input table for Input parameter
READ TABLE int_inval with key name = 'LTAP-NLPLA' .
check sy-subrc eq 0 .
SHIFT int_inval-value left deleting leading space.
w_nlpla = int_inval-value.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = w_nlpla
IMPORTING
OUTPUT = w_nlpla
READ TABLE int_outval index 1.
int_outval-value = w_nlpla+7(3).
modify int_outval index 1.
ENDFORM.
and in the change editor of form layout.
DEFINE &LAST_3& = ' '.
PERFORM LAST_3 IN PROGRAM ZMSPERFORMS_TRANSFER_ORDER
USING <AP-NLPLA&
CHANGING &LAST_3&
ENDPERFORM
I am not able to get the last 3 digits of delivery number printed.
Try adding the same subroutine in a report program instead of a subroutine pool..And try to print the form..
The sap help uses report program for storing the subroutine..
http://help.sap.com/saphelp_40b/helpdata/en/d1/803279454211d189710000e8322d00/content.htm
Thanks,
Naren
Similar Messages
-
Hai Everybody,
i have some problem in understanding in Transfer order Picklist form.
Please tell me, what are 'Part Number' , 'Legacy Number' & 'Serial Number' in the Transfer Order Picklist Print output form?
Thanks in Advance
VARMA.I believe it’s a volume license.
Wayne Robertson
IT/Help Desk/CNTRL OP
NBOME National Center for Clinical Skills Testing
101 West Elm Street, Suite 150
Conshohocken, PA 19428
610-825-6551 – 973-517-0081 cell
484-351-2245= direct#
cid:[email protected] -
Hi All,
I copied the standard SAP Smartform for Transfer Order from /smb26/*.I modified it.
I have given the name of the smart form at SPRO --> SAP REFERENCE IMG button --> Logistics Execution --> Warehouse Management --> Storage Units --> Activities > Define print control>Print Code.
and given the name of the standard print program at the print control.
If I click on this smartform and clicks on Form on Application Tool Bar's Form,its saying the SmartForm doesn't exists.
and I tried to execute from LT31 and LT0E,but invain.
Please kindly help me out.Your answers helps me a lot.
Thanks,
PraveenHi,
We are running 6.40 here and it still under form only points to SAPScript with no option of a Smartform. Following your exact steps listed, looks like you may have to stay with SAPScript unless you copy you program and hard-code a new for name.
Sorry -
TO(Transfer Order) wich FORM is used?
Hi,
I need to do some enhancement to standart FORM that is used with TO, transaction LT03 or LT0F.
But I dont know the name of these transactions LT03 or LT0F, can someone help plz?
Adibo..:)Hi,
Below are the enhaments available. for tcode LT03..
Exit Name Description
MWM2S001 Exit to Determine 2-Step Picking Characteristic
MWMBAP01 Enhancement for BAPI WarehouseTransOrder.GetDetail
MWMBAP02 Enhancement for BAPI WarehouseStock.GetDetail
MWMD0001 Transfer order print via RLVSDR40
MWMD0002 Transfer order print as multiple process with RLKOMM40
MWMIDI07 Enhancement for Output WMPIHU (Create Pick-HU) Inbound
MWMIDO11 Enhancement for message WMTORD: TO with several items
MWMIDO12 Enhancement for Output WMPIHU (Pick-HUs) Outbound
MWMIDO13 Extension for WMMBXY (subsequent tasks after goods movement)
MWMPP001 Enhancement WM/PP Interface (automatic TR generation)
MWMRF001 RF: Influence Display of material description
MWMRF100 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0100)
MWMRF101 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0101)
MWMRF102 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0102)
MWMRF104 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0104)
MWMRF105 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0105)
MWMRF106 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0106)
MWMRF107 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0107)
MWMRF108 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0108)
MWMRF151 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0151)
MWMRF152 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0152)
MWMRF153 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0153)
MWMRF170 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0170)
MWMRF202 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF203 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0203)
MWMRF204 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0204)
MWMRF205 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0205)
MWMRF212 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0212)
MWMRF213 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0213)
MWMRF221 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0221)
MWMRF302 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0302)
MWMRF303 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0303)
MWMRF304 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0304)
MWMRF305 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0305)
MWMRF312 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0312)
MWMRF313 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0313)
MWMRF321 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0321)
MWMRF400 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0400)
MWMRF402 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0402)
MWMRF403 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0403)
MWMRF404 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0404)
MWMRF405 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0405)
MWMRF406 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0406)
MWMRF410 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0410)
MWMRF411 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0411
MWMRF412 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0412)
MWMRF502 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0502)
MWMRF503 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0503)
MWMRF504 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0504)
MWMRF505 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0505)
MWMRF600 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0600)
MWMRF601 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0601)
MWMRF630 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0630)
MWMRF631 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0631)
MWMRF632 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0632)
MWMRF633 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0633)
MWMRF634 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0634)
MWMRF650 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0650)
MWMRF651 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0651)
MWMRF700 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF701 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0701)
MWMRF702 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF703 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0703)
MWMRF704 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0704)
MWMRF705 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0705)
MWMRF760 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0760)
MWMRF761 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0761)
MWMRF762 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0762)
MWMRF763 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0763)
MWMRF764 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0764)
MWMRF765 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0765)
MWMRF766 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0766)
MWMRF767 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0767)
MWMRF768 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0768)
MWMRF769 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0769)
MWMRF777 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0777)
MWMRF800 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0800)
MWMRF801 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0801)
MWMRF802 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0802)
MWMRF803 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0803)
MWMRF804 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0804)
MWMRF805 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0805)
MWMRF806 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0806)
MWMRF807 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0807)
MWMRF888 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0888)
MWMRF889 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF998 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0998)
MWMRF999 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0999)
MWMRFCOD Enhancement for function codedisabling
MWMRFDLV select delivery by user criteria
MWMRFPRT Enhancement for printing
MWMRFSSG user exit for sorting TOs in RF system-guided transaction
MWMRFUP Customer defined general purpose pushbutton called from scr.
MWMRP001 Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
MWMRP002 Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
MWMRP003 Customer Exit for Replenishment using RLLNACH1
MWMRP004 User Exit for Replenishment using RLLNACH4
MWMTO001 Enhancements for end of transfer order generation
MWMTO010 Exit: Calculation of Total Planned TO Processing Time
MWMTO011 Correction of Planned Processing Time for TO Item
MWMTO012 Correction of Sorting and Split Transfer Order
MWMTO013 Stock Removal for Sev. Storage Types as in Stringent FIFO
MWMTOAU3 Separate selection of posting changes for autom.TO creation
MWMTR001 Exits at the end of transfer rqmnt creation (IM,PP interf.)
Don't forget to reward if useful... -
Regarding TO (Transfer Order) to be confirmed collectively
Hello Gentlemen,
Can any body advise how to confirm the TO (transfer order) collectively is there any specific transaction for this process.
through LT12 can confirm individual but I am looking for collective confirmatiom.
Appreciate your help onthis......
regards
rkHello,
It is possible to confirm TO in mass with transaction LL01.
You need first to :
configure warehouse activity monitoring and define for exemple that unconfirmed TOs must appears in the warehouse monitor 15 minutes after their creation.
run report RLLL01SE in order to refresh the list of unconfirmed TOs.
Then run LL01 :
Select "unconfirmed TO" + select the TOs to confirm in mass by their movement type (double clic on the lines you want to confirm until you have the TO list).
Select the TOs to be confirmed and do "Goto" + "confirm TO in background"
Rgds,
Philippe -
How to transfer the stock form Project stock to Sale order stock
Hi
How to transfer the stock form Project stock to Sale order stock
I tried to do this with movement type 413Q
System is giving me error
Valuated project stock not allowed with customer stock.
Message no. KI346
How to do this
Thanks
NKYou can use Mov Type 412-Q
412 Q Transfer posting project to own - reversal
Thanks
Rajesh -
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 -
Hi gurus,
Please can any one tell me the Print program name and Form Routine for OutBound Transfer Order. And also tell me the in which output types i can attach these Print Program name and Form Name .. I created TO by using LT03.For this transaction I need Out put types..
Please can any one give the solution.....
Thanks in Advance
Thanks and Regards
Srihari..hi Ramesh,
Check the following:
1. Item category pirkcing relevance
2. Wear house no assignemnt
3. stock availability
4. Delivery - header - processing status
Once To is created it depends on whether it is single step picking or 2 step if 2 step in go to LT12 and do confirmation.
Then if packing is mandetory then you need todo packing and then PGI (VL02n) and then do VF01 invoice
Reward if it helps
Regards
Srini -
Transfer Order Printing using smart forms
Hi All
Our requirement is to print Transfer Order ( WM ) for Goods Receipt & Delivery using Smart forms.
Can we change the existing standard format (SAP script ) and use our own form(smart form ) to include some other data & print.
If possible how to replace the SAP script to Smart form.
Request someone could guide in detail.
Thanks in advance.
SamsonHi
When you create Smartform try to replace it in customizing OMLV. Not sure if it will work as it refers to Sap Scirpt in help description.
It is also possible to write Z program for TO printing and hardcode SmartForm there.
Regards
Mariusz -
Create collective Transfer order from collective outbound del?
Hello All
I created a group of deliveries and I got two outbound documents, now I want to create a collective Transfer order it gives me an error does not exist in T311 however the individual outbound delivery whiten the group could be picked
Can any one help me to solve this
Regards
Jacopo Francoishi
Transfer order will create based on delivery document . U got two delivery document number.
So goto LT03
enter delivery document number
execute save.
again goto LT03
enter another delivery document number execute, save it
regards
krishna -
Regarding Print of Single Form for multiple Transfer Order ( LT03 )
Hi All,
When user creates Transfer Order and if transfer order items are more than 22 then split of Transfer Order occurrs and multiple TO's get created in system. The standard prog. RLVSDR40 prints form for each TO's , however the requirment is to print only one form for multiple TO ( Actually TO Form containes info. abt delivery, but triggering point should be from TO creation ) .
There is one prog. RLKOMM40 which is used for multiple processing, whether this prog. will be useful for above requirement. Or is there any exit available for above requirement .
Thanks for help.Hi,
is there any routines used in Copy controls from order - delivery .- re-check once.
as your post, everything seems fine. I didnt see any reason for not creating single delivery.
is it happening only with this customer or respective ship to's? if yes, something gone wrong in CMR - i.e. complete delivery / order combination etcc., ( just an assumption)
Regards,
ReazuddinMD -
How to create collective Transfer order for a collective outbound delivery?
Hello All
I created a group of deliveries and I got two outbound documents, now I want to create a collective Transfer order it gives me an error does not exist in T311 however the individual outbound delivery whiten the group could be picked
Can any one help me to solve this
Regards
Jacopo Francoishi
Transfer order will create based on delivery document . U got two delivery document number.
So goto LT03
enter delivery document number
execute save.
again goto LT03
enter another delivery document number execute, save it
regards
krishna -
IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq
Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===> Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03 Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20 VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20 VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24 POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PMIDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned. -
How can i display the MRP controller in transfer order print?
Dear all:
When i print the transfer order(Tcode: LT31) ,i want to display the MRP controller in the output form.
How can i get that ?
I found the user exit MWMD0001 and add the code in the include like this:
select single dispo from marc
where matnr = ltap-matnr
and werks = ltap-werks.
zdispo = marc-dispo.
But caz the "zdispo" could not been brought to the "print form " of the report RLVSDR40 which control the print LT31.So ,i failed.
Anyone advice?The problem is as zdispo is declared in your user exit it doesn't become available. Had it been declared variable in the include of the program for LT31 you would be able to use it directly in the script.
Try doing this instead in your layout set.
/: PERFORM MRP_CONTROLLER IN PROGRAM ZABCXYZ
/: USING <AP-MATNR&
/: USING <AP-WERKS&
/: CHANGING &ZDISPO&
/: ENDPERFORM
in your program ZABCXYZ.
FORM MRP_CONTROLLER tables in_par structure itcsy
out_par structure itcsy.
tables: marc.
data: matnr like marc-matnr.
data: werks like marc-werks.
READ TABLE IN_PAR WITH KEY LTAP-MATNR.
CHECK SY-SUBRC = 0.
MATNR = IN_PAR-VALUE.
READ TABLE IN_PAR WITH KEY LTAP-WERKS.
CHECK SY-SUBRC = 0.
WERKS = IN_PAR-VALUE.
select single dispo from marc
where matnr = ltap-matnr
and werks = ltap-werks.
IF SY-SUBRC = 0.
READ TABLE OUT_PAR WITH KEY ZDISPO.
CHECK SY-SUBRC = 0.
OUT_PAR-VALUE = MARC-DISPO.
ELSE.
CLEAR OUT_PAR-VALUE.
ENDIF.
MODIFY OUT_PAR INDEX SY-TABIX.
ENDFORM.
This should work. -
Update tasks - Transfer Order creation.
I have an issue in our production environment where in some situations a Transfer Order (TO) is created with missing storage handling unit information. This only happens intermittently, and when the TO is cancelled and re-created, it is created with the correct storage unit information.
I have looked at the TO creation function l_to_create_int and it is called from within an update function module l_communication_to_create. The l_to_create_int function is not called within an update task. The function within l_to_create_int which creates the storage handling unit is an update function module (function L_TA_HINZUFUEGEN).
So my question is, what happens when you have a combination of function modules called as an update and function modules called normally? Will the updates in the function called normally update outside of the update task commit? I'm beginning to think that the problem may be caused by inconsistencies in when updates are completed by the program.
I'd greatly appreciate any help or guidance regarding this issue.
Kind regards,
James Mandikos.Hi James,
You are correct, a function module must be explicitly be called in 'UPDATE TASK' for it to be executed in the update task (regardless of the settings flagged in SE37).
If, however, it is called in UPDATE TASK there are four possible settings you can have in SE37 which each behave differently (as of the release I am looking at at the moment - R/3 4.7).
Here is my understanding of how the settings behave:
<b>Start immed.</b>
Will run in a V1 update process together with all other update functions called in the same LUW with Start immed. flagged.
<b>Immediate start, no restart</b>
As above, but cannot be reprocessed via transaction SM13 in the case of error (but can be viewed).
<b>Start delayed</b>
Will run in a V2 update process individually.
<b>Coll.run</b>
Will run in a V2 update process toegether with all other update functions called in the same LUW with Coll.run flagged.
So given the data you have provided both your function modules should be running in a collective V1 process, and therefore if one failed then the whole transaction should have been rolled back (and hence this does not explain your problem).
<b>BUT</b> what may be happening is that for whatever reason the transaction fails (maybe due to heavy system load) and either your system admin (or an autmated job) is pushing through the error in SM13. As the function L_TA_HINZUFUEGEN is flagged as immediate start, no restart then it will not be processed and the L_TO_CREATE_INIT will be. This could exactly explain your problem.
Hope that makes things clearer.
Cheers,
Brad
Maybe you are looking for
-
I really hope someone can help me. I've been having an issue with apps on my MBP crashing for like 9 months and it's getting worse and I'm losing my mind! It started with Firefox. Everything will be going along fine, and then suddenly I'll try to scr
-
Have I bricked my motherboard?
Hello! I got the P67A-GD55 REV B3 which has worked good for the last years, but I could never overclock my i5 2500K processor. I read up about it and it was becuase I used the 4.3 version of the bios. I read a post on this forums saying that I should
-
Error in First step of Process Chain
Hi everybody, i have created a process chain with a start process (direct scheduling) to InfoPackage to load into InfoCube-so delete indexes and generate indexes were automatically inserted becoz of default chain option. i have checked the chain-- th
-
How to compare values in collection.
Hi, I am using oracle 11g XE, I am doing a validation using bulk collect collection. DECLARE TYPE TEM IS TABLE OF VARCHAR2(1000); EM TEM; P_MAIL VARCHAR2(1000); BEGIN P_MAIL := UPPER('[email protected]'); SELECT EMAIL BULK COLLECT INTO EM FROM SELECT
-
I downloaded IOS6 to my ipad2...since then the Pentix Free app. has not been been behaving the same Is this a problem with the upgraded IOS?