PO print out of delivery schedule
Hi,
Suppose I am generating a PO , in some cases I will be giving delivery schedule for some items in item details.
I want this to come in the print out.
But its not coming .
Please advise.
regards,
Hi
You can include logic with the help of Developre, If information is there in EKET for Purchase order ask him to include in print.
regards
Srinivas
Similar Messages
-
Print out the delivery schedule item wise
Hi friends..
can any one pl tell me how to take the printout of the delivery schedules item wise.
i have checked the ME80RN but it doesnt work for me.
client want to print delivery schedule not SCHEDULING AGGREMENT.
Your help will be highly appreciated..with points..
Regards,
AnilHi,
Hope you can create an access sequence with material as a field and create a condition record based on this...
Bcoz mess determination takes place at header level.
Reg,
Deepak -
Allow buyer to suppress printing of item delivery schedule on PO
Gurus,
Is it possible to allow buyer to suppress printing of item delivery schedule on PO. If possible can you please propose me a solution.
Regardsnot with std config for PO creation but can be possible for PO changes
by seeting in the SPRO
MM-Purchasing-messages-fields relevant for printout changes
here u can do the settings for PO -
Dear All.
Till this day the duty-form for a company were performed through a
special Form Program, it is performed via processing routines.
The first Form Routine's name is entry.
Form was printed-out for each Transport up to now.
Current Requirements are for next time as follows:
Printing out one form for every delivery (shipment) instead of
for each Transport as so far. Please notice one Transport may
consist of many deliveries (Shipment). 1 Transport : n Shipment.
DATA:
lc_wa_usrdata TYPE /Z2a/ty_lw_usrdata.
INCLUDE rvadtabl.
SET EXTENDED CHECK OFF.
TABLES: vbpla, thead, ttxer, ttxit, t005, vbddl, stxh, sadr."SADR40A
INCLUDE vttkdata. "Shipment Header
INCLUDE vttsdata. "Shipment Segment
INCLUDE vttpdata. "Shipment Items
INCLUDE vbpadata. "Partner
INCLUDE vtfadata. "Flow
INCLUDE sadrdata. "Address
INCLUDE vtlfdata. "Delivery Selection
INCLUDE vsedata. "shipping units
INCLUDE rv56acom. "I/O-Structure
SET EXTENDED CHECK ON.
TABLES: /Z2a/tv_schein.
FORM entry USING return_code us_screen.
DATA: lf_retcode TYPE sy-subrc.
screen = us_screen.
PERFORM processing USING us_screen
CHANGING lf_retcode.
IF lf_retcode NE 0.
return_code = 1.
ELSE.
return_code = 0.
ENDIF.
ENDFORM.
FORM processing USING proc_screen
CHANGING cf_retcode.
DATA: ls_print_data_to_read TYPE ledlv_print_data_to_read.
DATA: ls_dlv_delnote TYPE ledlv_delnote.
DATA: lf_fm_name TYPE rs38l_fnam.
DATA: ls_control_param TYPE ssfctrlop.
DATA: ls_composer_param TYPE ssfcompop.
DATA: ls_recipient TYPE swotobjid.
DATA: ls_sender TYPE swotobjid.
DATA: lf_formname TYPE tdsfname.
DATA: ls_addr_key LIKE addr_key.
DATA: ls_header LIKE /Z2a/ss_pv_kopf.
DATA: tb_daten LIKE /Z2a/ss_pv_daten OCCURS 1.
DATA: lc_va_lfnr TYPE nrlevel.
DATA: lc_va_year TYPE char4.
DATA: lc_va_keyseg_pv TYPE /dca/p000_keyseg.
DATA: lc_tb_bwdat_pv TYPE /dca/p000_ty_tb_bwdat.
DATA: lc_wa_bwdat_pv TYPE /dca/p000_ty_wa_bwdat.
DATA: lc_wa_bwm_res_pv TYPE /Z2a/dat_cu_pvschein.
DATA: lc_va_lifnr TYPE kunnr.
DATA: lc_va_nr TYPE nrnr.
DATA: lc_va_anz TYPE /Z2a/anz_pv.
DATA: lc_va_no TYPE /Z2a/anz_kein_pv.
DATA: lc_wa_pvschein LIKE /Z2a/tv_schein.
DATA: lc_va_line LIKE sy-tabix.
DATA: lc_va_flag_zoll TYPE segal,
lc_va_rqident TYPE rspoid,
lc_va_vsart TYPE vsarttr,
lc_va_tknum TYPE tknum.
DATA: lc_va_obj TYPE nrobj.
DATA: lc_va_printer TYPE rspopname.
DATA: lc_va_pv_kz TYPE char4.
DATA: lc_va_tplst TYPE tplst.
* SmartForm from customizing table TNAPR
lf_formname = tnapr-sform.
* determine print data
PERFORM set_print_data_to_read USING lf_formname
CHANGING ls_print_data_to_read
cf_retcode.
IF cf_retcode = 0.
* select print data
PERFORM get_data_pv TABLES tb_daten
CHANGING ls_header
lc_va_flag_zoll
lc_va_vsart
lc_va_tplst
cf_retcode.
ENDIF.
lc_va_tknum = nast-objky.
IF cf_retcode = 0.
ELSE.
PERFORM protocol_nast_update.
cf_retcode = 4.
EXIT.
ENDIF.
IF cf_retcode = 0.
* determine smartform function module for delivery note
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
EXPORTING formname = lf_formname
IMPORTING fm_name = lf_fm_name
EXCEPTIONS no_form = 1
no_function_module = 2
OTHERS = 3.
IF sy-subrc <> 0.
ENDIF.
ENDIF.
DESCRIBE TABLE tb_daten LINES lc_va_line.
IF lc_va_line <> 0.
lc_va_pv_kz = 'JA'.
SELECT SINGLE lifnr
FROM vtpa
INTO lc_va_lifnr
WHERE vbeln = nast-objky
AND parvw = 'YL'.
lc_va_keyseg_pv = ls_header-kunnr.
lc_va_keyseg_pv+10(10) = lc_va_lifnr.
lc_va_keyseg_pv+20(2) = lc_va_vsart.
lc_va_keyseg_pv+22(4) = lc_va_pv_kz.
CALL FUNCTION '/ZTR/P000_MCDATA_FROM_'
EXPORTING
cv_va_keytyp = '/Z2a/KEY_CU_PVSCHEIN'
cv_va_keyseg = lc_va_keyseg_pv
TABLES
cr_tb_bwdat = lc_tb_bwdat_pv.
IF lc_tb_bwdat_pv[] IS INITIAL.
cf_retcode = 4.
ELSE.
LOOP AT lc_tb_bwdat_pv INTO lc_wa_bwdat_pv.
lc_wa_bwm_res_pv = lc_wa_bwdat_pv-datseg.
lc_va_obj = lc_wa_bwm_res_pv(10).
lc_va_nr = lc_wa_bwm_res_pv+10(2).
lc_va_anz = lc_wa_bwm_res_pv+12(8).
lc_va_printer = lc_wa_bwm_res_pv+20(4).
SELECT SINGLE pvno
FROM /Z2a/tv_schein
INTO lc_va_lfnr
WHERE tknum = nast-objky.
IF sy-subrc = 0.
ELSE.
CALL FUNCTION 'NUMBER_GET_NEXT'
EXPORTING
nr_range_nr = lc_va_nr
object = lc_va_obj
IMPORTING
number = lc_va_lfnr
IF sy-subrc <> 0.
ENDIF.
ENDIF.
ENDLOOP.
ENDIF.
* call smartform delivery note
ls_composer_param-tddest = lc_va_printer.
* ls_control_param-device = lc_va_printer.
lc_va_year = sy-datum(4).
PERFORM set_print_param USING ls_addr_key
lc_va_lfnr
CHANGING ls_control_param
ls_composer_param
ls_recipient
ls_sender
cf_retcode.
lc_wa_usrdata-mandt = sy-mandt.
lc_wa_usrdata-udate = sy-datum.
lc_wa_usrdata-uzeit = sy-uzeit.
lc_wa_usrdata-usr = sy-uname.
lc_wa_usrdata-sysid = sy-sysid.
DO lc_va_anz TIMES.
CALL FUNCTION lf_fm_name
EXPORTING
archive_index = toa_dara
archive_parameters = arc_params
control_parameters = ls_control_param
mail_recipient = ls_recipient
mail_sender = ls_sender
output_options = ls_composer_param
user_settings = ' '
ls_header = ls_header
lc_va_lfnr = lc_va_lfnr
lc_va_year = lc_va_year
lc_va_tplst = lc_va_tplst
lc_wa_usrdata = lc_wa_usrdata
TABLES
tb_daten = tb_daten
EXCEPTIONS formatting_error = 1
internal_error = 2
send_error = 3
user_canceled = 4
OTHERS = 5.
IF sy-subrc <> 0.
ENDIF.
ENDDO.
ELSE.
lc_va_pv_kz = 'NEIN'.
SELECT SINGLE lifnr
FROM vtpa
INTO lc_va_lifnr
WHERE vbeln = nast-objky
AND parvw = 'YL'.
lc_va_keyseg_pv = ls_header-kunnr.
lc_va_keyseg_pv+10(10) = lc_va_lifnr.
lc_va_keyseg_pv+20(2) = lc_va_vsart.
lc_va_keyseg_pv+22(4) = lc_va_pv_kz.
CALL FUNCTION '/ZTR/P000_MCDATA_FROM_'
EXPORTING
cv_va_keytyp = '/Z2a/KEY_CU_PVSCHEIN'
cv_va_keyseg = lc_va_keyseg_pv
TABLES
cr_tb_bwdat = lc_tb_bwdat_pv.
IF lc_tb_bwdat_pv[] IS INITIAL.
cf_retcode = 4.
ELSE.
LOOP AT lc_tb_bwdat_pv INTO lc_wa_bwdat_pv.
lc_wa_bwm_res_pv = lc_wa_bwdat_pv-datseg.
lc_va_obj = lc_wa_bwm_res_pv(10).
lc_va_nr = lc_wa_bwm_res_pv+10(2).
lc_va_anz = lc_wa_bwm_res_pv+12(8).
lc_va_printer = lc_wa_bwm_res_pv+20(4).
SELECT SINGLE pvno
FROM /Z2a/tv_schein
INTO lc_va_lfnr
WHERE tknum = nast-objky.
IF sy-subrc = 0.
UPDATE /Z2a/tv_schein
SET flag_pv = ' '
WHERE tknum = nast-objky.
ELSE.
* laufende nummer füllen, bei keinen PV-Teilen Nummernkreis 99
CALL FUNCTION 'NUMBER_GET_NEXT'
EXPORTING
nr_range_nr = lc_va_nr
object = lc_va_obj
* QUANTITY = '1'
* SUBOBJECT = ' '
* TOYEAR = '0000'
* IGNORE_BUFFER = ' '
IMPORTING
number = lc_va_lfnr
* QUANTITY =
* RETURNCODE =
* EXCEPTIONS
* INTERVAL_NOT_FOUND = 1
* NUMBER_RANGE_NOT_INTERN = 2
* OBJECT_NOT_FOUND = 3
* QUANTITY_IS_0 = 4
* QUANTITY_IS_NOT_1 = 5
* INTERVAL_OVERFLOW = 6
* BUFFER_OVERFLOW = 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.
ENDLOOP.
lc_va_year = sy-datum(4).
ls_composer_param-tddest = lc_va_printer.
PERFORM set_print_param USING ls_addr_key
lc_va_lfnr
CHANGING ls_control_param
ls_composer_param
ls_recipient
ls_sender
cf_retcode.
lc_wa_usrdata-mandt = sy-mandt.
lc_wa_usrdata-udate = sy-datum.
lc_wa_usrdata-uzeit = sy-uzeit.
lc_wa_usrdata-usr = sy-uname.
lc_wa_usrdata-sysid = sy-sysid.
DO lc_va_anz TIMES.
CALL FUNCTION lf_fm_name
EXPORTING
archive_index = toa_dara
archive_parameters = arc_params
control_parameters = ls_control_param
mail_recipient = ls_recipient
mail_sender = ls_sender
output_options = ls_composer_param
user_settings = ' '
ls_header = ls_header
lc_va_lfnr = lc_va_lfnr
lc_va_year = lc_va_year
lc_va_tplst = lc_va_tplst
lc_wa_usrdata = lc_wa_usrdata
TABLES
tb_daten = tb_daten
EXCEPTIONS formatting_error = 1
internal_error = 2
send_error = 3
user_canceled = 4
OTHERS = 5.
IF sy-subrc <> 0.
ENDIF.
ENDDO.
ENDIF.
ENDIF.
SELECT SINGLE *
FROM /Z2a/tv_schein
INTO lc_wa_pvschein
WHERE tknum = nast-objky.
IF sy-subrc = 0.
ELSE.
IF NOT lc_va_lfnr IS INITIAL.
lc_wa_pvschein-mandt = sy-mandt.
lc_wa_pvschein-tknum = nast-objky.
INSERT INTO /Z2a/tv_schein
VALUES lc_wa_pvschein.
UPDATE /Z2a/tv_schein SET
pvno = lc_va_lfnr
vsart = lc_va_vsart
exti1 = ls_header-schiffname
signi = ls_header-siegel
flag_zoll = lc_va_flag_zoll
exti2 = ls_header-contnr
lifex = ls_header-mbcnr
dalen = ls_header-dalen
dptbg = ls_header-dptbg
kunnr = ls_header-kunnr
add03 = ls_header-add03
parnr = lc_va_lifnr
datum_druck = sy-datum
uzeit_druck = sy-uzeit
ernam_druck = sy-ucomm
WHERE tknum = nast-objky.
IF tb_daten IS INITIAL.
UPDATE /Z2a/tv_schein SET
flag_pv = ' '
WHERE tknum = nast-objky.
ELSE.
UPDATE /Z2a/tv_schein SET
flag_pv = 'X'.
ENDIF.
ENDIF.
ENDIF.
* get SmartForm protocoll and store it in the NAST protocoll
* PERFORM ADD_SMFRM_PROT. DEL_HP_335958
ENDFORM.
FORM get_data_pv TABLES lc_tb_daten
CHANGING cs_header TYPE /Z2a/ss_pv_kopf
lc_va_flag_zoll TYPE segal
lc_va_vsart TYPE vsarttr
lc_va_tplst TYPE tplst
cf_retcode.
TYPES: BEGIN OF ty_wa_vbeln,
vbeln TYPE vbeln_vl,
END OF ty_wa_vbeln,
ty_tb_vbeln TYPE STANDARD TABLE OF ty_wa_vbeln
WITH DEFAULT KEY
INITIAL SIZE 0,
ty_wa_lips LIKE lips,
ty_tb_lips TYPE STANDARD TABLE OF ty_wa_lips
WITH DEFAULT KEY
INITIAL SIZE 0.
DATA: lc_tb_cond LIKE /Z2a/ss_pv_daten OCCURS 1.
DATA: lc_wa_daten TYPE /Z2a/ss_pv_daten.
DATA: lc_wa_cond TYPE /Z2a/ss_pv_daten.
DATA: lc_va_tknum TYPE tknum,
lc_tb_lips TYPE ty_tb_lips,
lc_wa_lips TYPE ty_wa_lips,
lc_va_kunnr TYPE kunnr,
lc_va_pvvkz TYPE /Z2a/pvvkz,
lc_va_exprf TYPE exprf,
lc_va_matnr TYPE matnr,
lc_va_menge TYPE lfimg.
DATA: lc_tb_vbeln TYPE ty_tb_vbeln,
lc_wa_vbeln TYPE ty_wa_vbeln,
lc_va_land1 TYPE land1,
lc_va_lifnr TYPE lifnr.
DATA: lc_va_exnum TYPE exnum.
DATA: lc_va_keyseg TYPE /dca/p000_keyseg.
DATA: lc_tb_bwdat TYPE /dca/p000_ty_tb_bwdat.
DATA: lc_wa_bwdat TYPE /dca/p000_ty_wa_bwdat.
DATA: lc_wa_bwm_result TYPE /Z2a/dat_cu_pvabwicklung.
DATA language LIKE nast-spras.
DATA shipment_number LIKE vttk-tknum.
CLEAR cf_retcode.
* get data
language = nast-spras.
shipment_number = nast-objky.
CALL FUNCTION 'RV_SHIPMENT_PRINT_VIEW'
EXPORTING
shipment_number = shipment_number
option_tvtk = 'X' "Shipmenttype J/N
option_ttds = 'X' "Disposition J/N
language = language
option_items = 'X' "Transport Items J/N
option_segments = 'X' "Transport Segments J/N
option_partners = 'X' "Partners J/N
option_sales_orders = 'X' "Sales orders J/N
option_export_data = 'X' "Export data J/N
option_packages = 'X' "Packages J/N
option_flow = ' ' "Flow J/N
option_no_refresh = ' ' "Refresh Tables J/N
IMPORTING
f_vttkvb = vttkvb "Shipment Header
f_tvtk = tvtk "Shipmenttype
f_tvtkt = tvtkt "Description Shipmenttype
f_ttds = ttds "Disposition
f_ttdst = ttdst "Description Disposition
f_vbpla = vbpla "Packages
TABLES
f_vttp = xvttp "Shipment Items
f_trlk = slk "Delivery
f_trlp = slp "Delivery Item
f_vtts = xvtts "Shipment Segments
f_vtsp = xvtsp "Segments/Items
f_vbpa = xvbpa "Partner
f_vbadr = xvbadr "Address
f_vtfa = xvtfa "Flow
f_vbplk = xvbplk "Shipment Unit Header
f_vbplp = xvbplp "Shipment Unit
f_vbpls = xvbpls "Shipment Unit Sum
EXCEPTIONS
not_found = 1.
cs_header-tknum = nast-objky.
cs_header-schiffname = vttkvb-exti1.
cs_header-abfahrt = vttkvb-dptbg.
cs_header-contnr = vttkvb-exti2.
cs_header-normt = vttkvb-add01.
cs_header-siegel = vttkvb-signi.
cs_header-gewbr = vttkvb-text2.
cs_header-gewnt = vttkvb-text3.
cs_header-dalen = vttkvb-dalen.
cs_header-dptbg = vttkvb-dptbg.
cs_header-add03 = vttkvb-add03.
lc_va_tplst = vttkvb-tplst.
lc_va_vsart = vttkvb-vsart.
SELECT vbeln
FROM vttp
INTO TABLE lc_tb_vbeln
WHERE tknum = lc_va_tknum.
LOOP AT lc_tb_vbeln INTO lc_wa_vbeln.
SELECT SINGLE kunnr lifex
FROM likp
INTO (lc_va_kunnr, cs_header-mbcnr)
WHERE vbeln = lc_wa_vbeln-vbeln.
SELECT *
FROM lips
INTO TABLE lc_tb_lips
WHERE vbeln = lc_wa_vbeln-vbeln.
ENDLOOP.
LOOP AT lc_tb_lips INTO lc_wa_lips.
SELECT SINGLE pvvkz
FROM /Z2a/ldm_kun
INTO lc_va_pvvkz
WHERE kunnr = lc_va_kunnr.
IF lc_va_pvvkz NE 'X'.
cf_retcode = 4.
EXIT.
ELSE.
SELECT SINGLE exnum segal
FROM eikp
INTO (lc_va_exnum, lc_va_flag_zoll)
WHERE refnr = lc_wa_lips-vbeln.
SELECT SINGLE exprf
FROM eipo
INTO lc_va_exprf
WHERE exnum = lc_va_exnum
AND expos = lc_wa_lips-posnr.
lc_va_keyseg = lc_va_exprf.
CALL FUNCTION '/ZTR/P000_MCDATA_FROM_'
EXPORTING
cv_va_keytyp = '/Z2a/KEY_CU_PVABWICKLUNG'
cv_va_keyseg = lc_va_keyseg
TABLES
cr_tb_bwdat = lc_tb_bwdat.
IF NOT lc_tb_bwdat[] IS INITIAL.
LOOP AT lc_tb_bwdat INTO lc_wa_bwdat.
lc_wa_bwm_result = lc_wa_bwdat-datseg.
IF lc_wa_bwm_result-pv_relevant = 'X'.
* Kumulieren
lc_wa_cond-matnr = lc_wa_lips-matnr.
SELECT SINGLE maktx
FROM makt
INTO lc_wa_cond-arktx
WHERE matnr = lc_wa_lips-matnr
AND spras = 'DE'.
lc_wa_cond-menge = lc_wa_lips-lfimg.
lc_wa_cond-me = lc_wa_lips-meins.
COLLECT lc_wa_cond INTO lc_tb_cond.
ENDIF.
ENDLOOP.
ENDIF.
ENDIF.
ENDLOOP.
cs_header-kunnr = lc_va_kunnr.
SELECT SINGLE name1 name2 land1
INTO (cs_header-name1,
cs_header-name2,
lc_va_land1)
FROM kna1
WHERE kunnr = lc_va_kunnr.
SELECT SINGLE landx
INTO cs_header-land
FROM t005t
WHERE spras = sy-langu
AND land1 = lc_va_land1.
* Sortieren Aufsteigend nach Materialnr
SORT lc_tb_cond ASCENDING BY matnr.
* Übergabe an Ausgabetabelle
LOOP AT lc_tb_cond INTO lc_wa_cond.
MOVE-CORRESPONDING lc_wa_cond TO lc_wa_daten.
APPEND lc_wa_daten TO lc_tb_daten.
ENDLOOP.
ENDFORM. " get_data_spat
FORM set_print_data_to_read
USING if_formname LIKE tnapr-sform
CHANGING cs_print_data_to_read TYPE ledlv_print_data_to_read
cf_retcode.
FIELD-SYMBOLS: <fs_print_data_to_read> TYPE xfeld.
DATA: lt_fieldlist TYPE tsffields.
DATA: ls_fieldlist TYPE LINE OF tsffields.
DATA: lf_field1 TYPE LINE OF tsffields.
DATA: lf_field2 TYPE LINE OF tsffields.
DATA: lf_field3 TYPE LINE OF tsffields.
CALL FUNCTION 'SSF_FIELD_LIST'
EXPORTING
formname = if_formname
* VARIANT = ' '
IMPORTING
fieldlist = lt_fieldlist
EXCEPTIONS
no_form = 1
no_function_module = 2
OTHERS = 3.
IF sy-subrc <> 0.
cf_retcode = sy-subrc.
CLEAR lt_fieldlist.
ELSE.
* set print data requirements
LOOP AT lt_fieldlist INTO ls_fieldlist.
SPLIT ls_fieldlist AT '-' INTO lf_field1 lf_field2 lf_field3.
* <<<< START_OF_INSERTION_HP_350342 >>>>
IF lf_field1 = 'IS_DLV_DELNOTE' AND lf_field2 = 'IT_SERNR'.
lf_field2 = 'IT_SERNO'.
ENDIF.
* <<<< END_OF_INSERTION_HP_350342 >>>>
ASSIGN COMPONENT lf_field2 OF STRUCTURE
cs_print_data_to_read TO <fs_print_data_to_read>.
IF sy-subrc = 0.
<fs_print_data_to_read> = 'X'.
ENDIF.
ENDLOOP.
* header data is always required
cs_print_data_to_read-hd_gen = 'X'.
* adress is always required for print param
cs_print_data_to_read-hd_adr = 'X'.
* organisational data is always required for include texts
cs_print_data_to_read-hd_org = 'X'.
ENDIF.
ENDFORM. " set_print_data_to_read
*& Form set_print_param
* text
* -->P_LS_ADDR_KEY text
* <--P_LS_CONTROL_PARAM text
* <--P_LS_COMPOSER_PARAM text
* <--P_LS_RECIPIENT text
* <--P_LS_SENDER text
* <--P_CF_RETCODE text
FORM set_print_param USING is_addr_key LIKE addr_key
* lc_va_tknum
lc_va_lfnr TYPE nrlevel
CHANGING cs_control_param TYPE ssfctrlop
cs_composer_param TYPE ssfcompop
cs_recipient TYPE swotobjid
cs_sender TYPE swotobjid
cf_retcode TYPE sy-subrc.
DATA: ls_itcpo TYPE itcpo.
DATA: lf_repid TYPE sy-repid.
DATA: lf_device TYPE tddevice.
DATA: ls_recipient TYPE swotobjid.
DATA: ls_sender TYPE swotobjid.
DATA: lc_va_suffix TYPE rspo2name.
lf_repid = sy-repid.
CALL FUNCTION 'WFMC_PREPARE_SMART_FORM'
EXPORTING
pi_nast = nast
pi_addr_key = is_addr_key
pi_repid = lf_repid
IMPORTING
pe_returncode = cf_retcode
pe_itcpo = ls_itcpo
pe_device = lf_device
pe_recipient = cs_recipient
pe_sender = cs_sender.
SHIFT lc_va_lfnr LEFT DELETING LEADING '0'.
CONCATENATE 'PV' lc_va_lfnr INTO lc_va_suffix.
IF cf_retcode = 0.
MOVE-CORRESPONDING ls_itcpo TO cs_composer_param.
cs_composer_param-tdsuffix2 = lc_va_suffix.
cs_control_param-device = lf_device.
cs_control_param-no_dialog = 'X'.
cs_control_param-preview = screen.
cs_control_param-getotf = ls_itcpo-tdgetotf.
cs_control_param-langu = nast-spras.
ENDIF.
ENDFORM. " set_print_param
FORM protocol_nast_update.
CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
EXPORTING
msg_arbgb = '/Z2a/PVSCHEIN'
msg_nr = '001'
msg_ty = 'E'
* MSG_V2 = SYST-MSGV2
* MSG_V3 = SYST-MSGV3
* MSG_V4 = SYST-MSGV4
* MSG_V1 = SYST-MSGV1
EXCEPTIONS
OTHERS = 1.
ENDFORM.Hello!
I have to customize the enclosed source code so it does the following:
print out for each shipment (see FuBa:RV_SHIPMENT_PRINT_VIEW
parameter slp) really seperated by for every shipment item LIKP-VBELN
and not for the whole VTTP-TKNUM.
The parameter "slp" must be stripted so by leaving
of the routine "get_data_pv" has only the datas of the current
LIKP-VBELN, and in the next step taking the next LIKP-VBELN
and so on. Right now it performs only one time for one VTTP-TKNUM.
If you don't understand VTTP-TKNUM and LIKP-VBELN please refer
to Transaction SE11.
Reagrds
Ilhan -
PO print outs having delivery address as of storage location
Hello Experts,
What setting need to be done to have storage location address as delivery address in PO by default.In your print program pass values plant and storage location in table TWLAD and in that table you will get address number .Use this address number in ADRC table and get address details in PO output form.
Please explain above logic to your technical team and they will do program changes. -
Can we cancel the print out of a scheduled report?
Suppose a report is scheduled and configured to printer.
We want send a cancel command to the printer.
how can this be done?Hi Sriram,
Once you send any request to printer it will take it into printer buffer. You can't pass any command to cancell the printer buffer. You will have to go in printers and cancell the print job.
If you switch off the printer also the print que will wait till the printer comes in ready mode.
You will have to change the configuration of the scheduled report.
Hope this will help you.
Thanks,
Sastry -
Display only/Grey out Delivery Schedule tab in the PO
We are not going to use Delivery Schedule tab at all. Business wants us to Grey out the delivery schedule tab. Is it possible to make all fields under Delivery Schedule as display only? If yes, how can I do that? But, I don't want PO line qty to be grayed out.
Fields like, delivery date, scheld qty, stat.del date etc.
Thanks everyone.you better convince your business to wait for a couple months and then rethink this requirement.
You may not have the full understanding yet and have not made a lot experience.
in this tab you can add further requisitions to your PO item, you can close requisitions in case you order less than a requisition, you have to change the statistical delivery date in some case when you are using vendor evaluation, you may have to split the order quantity into several delivery dates if your vendor informs you that he cannot supply you at one time with all quantity.
Just to save you money that you may spend into a development which has to be turned off a little later. -
Delivery schedule print out and number
Dear Expert
Our client need to implement the scheduling agreement in the company , but the requirement as follows their are two dept one is for vendor dealing and our is meant for requirement generation , so scheduling agreement is generated by one dept and delivery schedule will be generated by other , is it possible to generate different for delivery schedule?/it not how can we configure the system as such when we release the delivery schedule on the basis of FRC release procedure then only print out should be generated for the deliverry schedule and print out should only consider those line item of delivery schedule which are release no other , i.e if for e.g for 1st month the delivery schedule is generated against the PR 's for different line item of Scheduling agreement , then only those item wil be consider which are release as per the FRC , then for the next delivery schedule only those item to be consider in the print out which are release 2nd time. how can we map this scenario in the system
Regards
farhanDear Expert
can we customize system as such that we cannot maintained delivery schedule before the release of the SA
Regards
farhan -
MRP keeps pushing delivery schedules out, refusing to firm them (ME33L)
I hope someone has seen something like this before and can let us know where to look. MRP keeps pushing our delivery schedules out even though it is recommending that they be rescheduled in. What we'd like to happen is for MRP to leave these schedules alone so that they would move inside the time fence and be firmed automatically. Here is what is happening:
Part X, MRP type P1, firming type 1, MRP group blank. Planning time fence 05/07/2007, available quantity -20.
Three schedule lines exist for 05/07/2007, two for 10 and another for 30.
MRP will run tonight. Processing Key = NEUPL, purch req = 2, sched lines = 3, MRP list = 1, planning mode = 2, scheduling = 2
Tomorrow, the planning time fence will be at 05/08/2007 and the three schedule lines will move out to 05/08/2007. The won't move inside the planning time fence and firm up. They SHOULD BE 05/07/2006 and firmed!
We originally thought that we may have to create a release with ME84 before these would firm, but it made no difference. They still won't firm unless someone manually changes the date on each and every schedule line.
Does anyone know what we can change or run to get these schedules to firm up instead of having them pushed out continually?Hello Randy,
thanks for the update. I didnt remenber this customizing indicator when posting.
Still wondering why planning matters here. I think it should have the same result for all planning modes. Of course planning mode 3 in general should be avoided for performance reasons.
For interested observers I attach the description for this setting in MRP customizing.
Regards, Martin
Indicator: Only Firm Transmitted Schedule Lines
In this step, you can set an indicator which is used to set only those schedule lines that have been transferred to the vendor.
You can firm schedule lines within the planning time fence (in the same way as planned orders or purchase requisitions) according to the master schedule item firming logic. The planning time fence is a number of days that is calculated into the future starting from the current date. Therefore, the last date of the planning time fence changes every day.
In the firming logic, existing schedule lines are also firmed as soon as they move into the planning time fence.
Schedule lines that lie outside the planning time fence and whose quantity is adjusted in the planning run due to a change of the requirements quantity are firmed with the new quantity as soon as the schedule lines move into the planning time fence.
The schedule lines are transferred to the vendor for the amount recorded in the stock/requirements list at the time of the data transfer.
If you only want to firm the schedule lines in the planning time fence that have been checked and transferred to the vendor, you can use the indicator, Only firm transmitted schedule lines. By selecting this indicator, the system only firms the schedule lines that have been sent to the vendor.
For schedule lines whose quantity has changed and which have moved into the planning time fence, the following occurs if this indicator has been set: if the MRP controller/purchaser does not confirm the procurement plan by sending the changed quantities to the vendor, the schedule line quantities that were sent to the vendor in the previous data transfer are firmed within the planning time fence. This guarantees that the system cannot firm any quantities that have not been checked. It also means that the vondor does not receive any messages for unchecked schedule line quantities.
Activities
Define the indicator per MRP group and allocate this MRP group to the materials for which this indicator is to be valid.
Further notes
The message transfer is a purchasing function. You can find it in the purchasing menu, Outline agreement -> Scheduling agreement -> Messages -> Print/transmit. -
Print out of Schedule Lines & Material reqt at subcontractor end.
Hi experts,
Presently we are using ME9E report for taking print out of scheduling agreement. In scheduling agreement, material wise / date wise R.M requirement at Subcontractor end is displayed as well as schedule lines material wise / date wise is displayed.
We do not find it user friendly. We are searching for following reports :
1. Datewise / Material wise requirement of R.M at subcontractor end should be displayed separately.
2. Schedule line qty date wise / material wise should be displayed separately.
Solutions / Suggestions will be highly appreciated.
Regards,
( Rajneesh Gulati )hi,
pl go with Y program -
Scheduling Agreement with print out
Hello
I created one Scheduling agreement for vendor A1 and created schedule lines .
in header Data of this Scheduling agreement i have mentioned the Invoicing party is B1
when i take the print out of Invoicing document the Vendor A1 disply , it is not taking the Invoicing party B1 i print out
i have defined in Patrner in that who is supplier, order , and who is invoicing party
that's$why iam search the header data of Scheduling agreement in that i got invoicing party is B1 is there, still in print out i got wrong vendor no why?
one thing is
this B1 is not defined for perticular Purchasing org, i ahve searched in LFM1 table, is this the reason
i have searched the out put determination for date 14.06.2007 here only partner is A1 is this a reason, shall we define the invoicing party in output determination
totaly i want the name of invoicing party in print out
regards
sapmanHi,
the partner functions only store the data (i.e. addresses etc.) and make it available for the print program.
You have to code the print program to get it to use the correct vendor for the addresses etc.
The invoicing party address is not normally referenced on the scheduling agreement prints because this si the address that the payment is made to and the address that sends the invoice to you. Why woukld you print the vendors invoice address or name on the scheduling agreement? It is the OA (Ordering Address) that is relevant for the print of the scheduling agreement or schedules.
So why would you print the invoicing vendor's details on a scheduling agreement print out?
Steve B -
Greyed out fields to be enabled in delivery schedule tab of ME21N & ME22N
Hi Gurus,
I need to make two fields in PO create and change tcode, to be made editable as they are greyed out for particular document type and item category combination. Please refer screenshots below:
Standard Order:
Framework Order:
I tried settings in 'Define Screen Layout at Document Level' for that field selection as well as in Edit system settings at the item detail level...but still the fields are in disabled mode only. Any help in this regard??
Thanks in advance...Hello Pramod,
As AKPT has pointed out, FO type documents are used for a broad framework type scenario, where most of the details are unknown at the time of releasing the PO.
The system by default allows standard, limit (B) and service (D) for such POs.
If you are trying to change the item category during creation (and not after the PO has history) please look at this IMG -> MM -> Purchasing -> Define Doc types -> Framework order FO -> Allowed Item categories.
I don't think delivery schedules are allowed for FO type orders. -
Print Preview of Out bound delivery is not available in VL71
Hi Experts,
I have created Outbound delivery with VL10B (against Purchase Order) and also set up output parameter in VL02N (Extra->elivery output -> Header)
Now I want to take Print out of this Outbound delivey in VL71 , I cant even see the Print preview. I have already maintained Output type , Access sequence and condition table in SPRO . I have also maintained condition record also (with delivery type and Shipping point).
Any help on thisCheck if output triggered successfully in delivery.
If yes, then please use indicator "Processing Mode" appropiately on the main selection screen of VL71.
If not, please see the error and try to resolve it.
Also check from main screen of VL02n where you enter delivery no, don't go inside the delivery screen, from main screen itself,
Outbound delivery> Issue Delivery output
Hope it helps
Regards
Anand Misra -
Sapscript - print out seperate labels for multiple delivery items
Hello,
we do have an output type that prints barcode labels for deliveries (VL02n).
Now if there are more than one delivery item on the delivery, it will only print out a label for the first item.
How can I trigger that all items will be printed out on a seperate label each?
thanks
AnneHi,
Just open the script which prints the lables and check for the variable name used for label printing
Check the script for variables and pass the value to that avriables and those to be declred in your print/driver program.
when you call write_from in the loop there you give a window name what ever the value in the variable it will pass to script
Regards
Krishna -
Version wise print out of Scheduling Agreement
Hi,
Client uses scheduling agreement extensively. One SA per annum per vendor is maintained as a policy. A number of items are included almost on a weekly basis. Some times, they miss to take the print out of say version 10 and currently the version is say 15. In some cases, this print out of version 10 might be lost in transit.
Now, user wants to take the print out of version 10 alone. Currently, the print out is designed such that the latest version (15) only can be printed with the corresponding change alone (or) the total SA can be printed including details as per current version (15).
We can not ask them to send the total SA print out as it runs into pages.
Please advise how can I take the print out of SA for version 10 alone, in the above case.
Thanks & Regards,
SivaTake the help from ABAPer and give your requirment to print the tax at item level.
Maybe you are looking for
-
Hard drive recovery(trying to save my life)
i have had my pavilion notebook for 18 months now. due to the fact of my job i travel a lot and always meant to back up my hard drive but never did. Now my hard drive is not working at all and needs to be replaced. I have a lot of precious photos a
-
My iPad mini is completely dead. I have tried all the reset methods to no avail. It has to be sent to Apple. Do I have to erase everything on it via iCloud beforehand? It might just be a dead battery so seems a bit extreme.
-
Can I rearrange the order of Menu, Bookmark, Tab, and Title bars?
Having the Bookmark Bar between the Tab & Title Bars and the page itself seems out of place to me. I would like the bars in the following order (top to bottom): Menu Bar, Bookmark Bar, Tab Bar, Title Bar Is it possible to arrange them in this manner?
-
Would you tell me how I could suppress a document in Adobe?
Hi, I would like to know how to suppress a document once it is filed in Adobe? thank you. magasinage
-
BO 4.0 save as csv file format issue
Hi All, We are using BO 4.0 Webi for reporting on SAP BW 7.3 system. Some of our reports have to be scheduled to bring the output in CSV file format. When I schedule the report in CSV format, the final output has data in two sets. The first set has t