Trigger Transaction code from BW to ECC

I am looking for a procedure for automation where in i need to trigger a transaction code in ECC as soon as the process chain starts in BW. so this is from BW to ECC
The results of the Tcode in ECC needs to be store so that later they can be validated with the BW report once the process chain is complete

Hello,
1) Define a Custom ABAP Program (eg : Z_EVENT_RAISE)..........call the FM : BP_EVENT_RAISE or RSSM_EVENT_RAISE..........and trigger an event towards BW .........specify BW as RFC destination...........
2) Create a R/3 Job in SM36>> use the Program Z_EVENT_RAISE ......
3) In BW schedule the PC..........and in the Start variant use this Event..........
ABAP code to trigger Process Chain (Weekdays)
Regards,

Similar Messages

Remove transaction codes from multiple roles at a time

Hello,
how to remove transaction codes from multiple roles at at time?
Thank you in Advance.

Hi Vanita,
Why do you want to remove a t-code from all the roles. Are you no longer going to use the t-code. If this is the case then you can lock the transaction code in T-code SM01 so that no one can use it. But this would effect other users as well, it should only be locked if no one should use the particular T-code.
Another alternative is to write a program to remove the particular T-Code from the table AGR_TCODES where the relation ship between the role and t-code is stored.
Thanks.

PFCG issue - removing transaction codes from menu and not clearing up the authorization tab

I’m using SAP ERP version ECC6 and EHP5 and also we have updated our system with the PSCD FI module.
I’m having the following issue in PFCG transaction code - I have created a new single role by copied other or from scratch and added few transaction codes into the menu. After that, I went in the authorization tab using the "Change Authorization Data" and I felled all the missing information until the role was green out. I generated the role then I totally went out. I come back to the same role that I created earlier and I did removed all the transaction codes from the menu and I did find the following:
- the Authorization tab light didn't change from green to red
- I went into the Authorization tab by "Change Authorization Data" and a part of the objects were still in.
Normally behave should be:
- when we remove one transaction code from the menu the light from Authorization tab should change from green to red. When you empty the menu then the light color should change also, but the authorization tab should be also empty.
Could please give me some idea how to do it next?

Hi Gabriela,
Most of the times standard roles contains manually added authorization objects. When ever you are creating a new role by copying the existing standard role so by default, these objects will come in to new role.
Now, coming to your role. After removing t code from role if nothing has changed in Authorization tab means.
Here are the possible reasons.
1. The t code which you have removed might not have any checked and maintained authorization objects, that's why your Authorization tab still in unchanged.
2. Rememeber, when ever you are adding or removing t code from menu always use expert mode for profile generation option along with "Read old status and merge with new data" Option.
This will bring the all checked and maintained data for each t code.
3. After removing the t codes from menu and if you generate the Authorization tab by using expert mode option still if you find authorization objects means, those are manually added authorization objects that's why those were not removed.
I hope this will give some clue to your issue.
Thanks,
Siva

Delete transaction codes from a role

Hi,
I want to delete 20 percent of the transaction codes from a role and I have to carry out this exercise for 20 to 30 roles, please let me know how to go about it.
I know that I can go to the each role and delete each transaction by transaction but this process appears to be very tedious and time consuming, kindly let me know if there is any other alternative for this.
Please help.
Thanks
Suresh

Hello Suresh,
First create single column internal table, for example ROLES which will hold all the ROLES for which you want to delete transaction codes. Read all the required ROLES into ROLES table.
Now, You can create internal table, for example ITAB1 for ROLES and TRANSACTION CODES and read required roles and transactikon code from AGR_TCODES table.
Now loop at ROLES.
Move all the records from ITAB1 to ITAB2 where AGR_NAME = ROLES. --> as ROLES is single column table.
 DESCRIBE TABLE ITAB2 LINES <count>.
 Now find 20 % of the total <count>.
 Now use delete table with from 1 to <result after %age>
..... Go for next ROLE.
endloop.
For example:
If total transaction cod efor particular ROLE are 10 then
20% of 10 will be 2 transaciton codes.
so you can delete table <table> name from 1 to 2.
Hope this helps.
Thanks,
Augustin.

Cross-System Copying of Transaction Types from CRM to ECC

Hi Gurus,
We have a requirement where we need to create followup transactions from CRM to ECC.
eg:- We want to create a Sales Order in ECC as a followup transaction to a Service Ticket in the CRM.
1) So please guide what needs to be done inside CRM.
2) Is there some specific list of ECC transactions which could be created as followup to a CRM transaction or any ECC transaction can be created as followup.
thanks for your help in advance.
rgrds,
Randhir

Dear Randhir,
You need to ensure that transaction type and item category of ECC and CRM are in Sync. Maintin followup of your transaction type.
Thanks and regards
Pankaj Kumar

Transaction codes from end user point of view

hi all,
I am expecting end user transaction codes of warehouse management.
I am familiar with materials management but looking to learn WM.
regards,
nitin patil

Hi refer bellow Tcodes,
WM
0.LI21 - Clear the stock from inventory
1.LB01 - Create Transfer Requirement
2.LB02 - Change transfer requirement
3.LB03 - Display Transfer Requirement
4.LB10 - TRs for Storage Type
5.LB11 - TRs for Material
6.LB12 - TRs and Posting Change for MLEat.Doc.
7.LB13 - TRs for Requirement
8.LD10 - Clear decentralized inventory difference
9.LD11 - Clear differences for decentral.sys.
10.LI01 - Create System Inventory Record
11.LI02 - Change System Inventory Record
12.LI03 - Display System Inventory Record
13.LI04 - Print System Inventory Record
14.LI05 - Inventory History for Storage Bin
15.LI06 - Block Storage types for annual invent.
16.LI11 - Enter Inventory Count
17.LI12 - Change inventory count
18.LI13 - Display Inventory Count
19.LI14 - Start Inventory Recount
20.LI20 - Clear Inventory Differences WM
21.LI21 - Clear Inventory Differences in MM-IM
22.LL01 - Warehouse Activity Monitor
23.LLVS - WM Menu
24.LN01 - Number Ranges for Transfer Requirement
25.LN02 - Number Ranges for Transfer Orders
26.LN03 - Number Ranges for Quants
27.LN04 - Number Ranges for Posting Changes
28.LN05 - Number Ranges for Inventory
29.LN06 - Number Ranges for Reference Number
30.LN08 - Number Range Maintenance: LVS_LENUM
31.LP10 - Direct picking for PO
32.LP11 - WM staging of crate parts WM运
33.LP12 - Staging release order parts (WM-PP)
34.LP21 - WM replenishment for fixed bins WM
35.LP22 - Replenishment Planning for Fixed Bins
36.LQ01 - Transfer Posting in Invent. Mgmt
37.LQ02 - Transfer Posting in Invent. Mgmt
38.LS01 - Create Warehouse Master Record
39.LS02 - Change Warehouse Master Record
40.LS03 - Display Warehouse Master Record
41.LS04 - Display Empty Storage Bins
42.LS05 - Generate Storage Bins
43.LS06 - Block Storage Bins
44.LS07 - Block Quants
45.LS08 - Block Storage Bins per Aisle
46.LS09 - Display Material Data for Storage Type
47.LS11 - Change storage bins (multiple proc.)
48.LS12 - Block Storage type
49.LS22 - Change Quants
50.LS23 - Display Quants
51.LS24 - Display Quants for Material
52.LS25 - Display Quants per Storage Bin
53.LS26 - Stock of Material
54.LS27 - Display Quants for storage unit
55.LS28 - Display storage units / bin
56.LS32 - Change storage unit
57.LS33 - Display storage unit
58.LS41 - List of control cycles for WIP loc
59.LT01 - Create Transfer Order
60.LT02 - Create TO for Inventory Difference
61.LT03 - Create TO from Delivery Note
62.LT04 - Create TO from TR
63.LT05 - Process Posting Change Notice
64.LT06 - Create TO for Material Document
65.LT07 - Create TO for mixed storage unit
66.LT08 - Manual addition to storage unit
67.LT09 - ID point function for storage units
68.LT0A - Pre-plan storage units
69.LT0B - Stock Placement of Shipping Units
70.LT0C - Stock Removal of Shipping Units
71.LT0D - Stock Transfer of Shipping Units
72.LT0E - Create Removal TO for 2-Step Picking
73.LT10 - Create Transfer Order from List
74.LT11 - Confirm Transfer Order Item
75.LT12 - Confirm Transfer Order
76.LT13 - Confirm TO for storage unit
77.LT14 - Confirm preplanned TO item
78.LT15 - Canceling transfer order
79.LT16 - Canceling TO for storage unit
80.LT17 - Single Entry of Actual Data
81.LT1A - Change Transfer Order
82.LT21 - Display Transfer Order
83.LT22 - Display Transfer Order / Storage Type
84.LT23 - Display Transfer Orders by Numbers
85.LT24 - Display Transfer Order / Material
86.LT25 - Display Transfer Order / Reference
87.LT26 - Transfer orders for storage bin
88.LT27 - Transfer order for storage unit
89.LT28 - Display Transfer Order / Reference
90.LT31 - Print TO Manually
91.LT32 - Print transfer order for storageunit
92.LT41 - Prepare TRs for Multiple Processing
93.LT42 - Create TOs by Multiple Processing
94.LT43 - Forming groups for deliveries
95.LT44 - Release for Multiple Processing
96.LT45 - Evaluation of reference numbers
97.LT51 - Maintain Missing Stock
98.LT63 - Control: Single Entry of Actual Data
99.LT64 - Single Entry of Actual Data
100.LT72 - Determine 2-step relevance
101.LT73 - Display 2-step
102.LU01 - Create Posting Change Notice
103.LU02 - Change Posting Change Notice
104.LU03 - Display Posting Change Notice
105.LU04 - Selection of Posting Change Notices
106.LX01 - List of Empty Storage Bins
107.LX02 - Inventory List
108.LX03 - Bin Status Report
109.LX04 - Capacity Used
110.LX05 - Block Bins in Bl.Storage w .Time Limt
111.LX06 - Inventory List for Fire Department
112.LX07 - Check storage
113.LX08 - Accident Regulations List
114.LX09 - Overview of All Transfer Requirements
115.LX10 - Activities per Storage Type
116.LX11 - Overview of Documents
117.LX12 - Document Overview: Landscape Format
118.LX13 - Analysis of Differences
119.LX14 - Analysis of Material Transfers
120.LX15 - Selection of Bins for Annual Inventory
121.LX16 - Selection of Bins for Continuous Inventory
122.LX17 - List of Inventory Differences
123.LX18 - Statistics of Inventory Differences
124.LX19 - Inventory Data Takeover by Batch Inp.
125.LX20 - Generate interim storage bins
126.LX21 - Pick List for Several Transfer Order
127.LX22 - Process Inventory from Overview
128.LX23 - Stock comparison IM - WM
129.LX24 - Display of Hazardous Material numbers
130.LX25 - Inventory Status
131.LX26 - Inventory in WM via cycle counting
132.LX27 - Stock levels by shelf life expiry date
133.LX28 - Relevant TO item for ext.system
134.LX29 - Fixed bin supervision
135.LX30 - Overview of WM messages ext.system
136.LX31 - Analysis of print control tables
137.LX32 - Archived transfer orders
138.LX33 - Archived transfer requirements
139.LX34 - Archived posting change notices
140.LX35 - Archived system inventory records
141.LX36 - Archived inventory histories
142.LX37 - Linked objects
143.LX38 - Check Report Customizing Strategy K
144.LX39 - Evaluation Reference No. for 2-S.Pck
145.LX40 - Material Situation Prod. Storage Bin
146.LX41 - Bin Status Report WM/PP Interface
147.LX42 - Evaluation PP Order from WM View
148.LX43 - Consistency Check for Control Cycles MCL9
WM: Material Plcmt/Removal:Selection
149.MCLD - WM: Material flow - Selection
150.MCLH - WM: Movement types - selection -
151.OL01 - Display / change LDK34 (bins)
152.OL02 - Display / change RLPLA (bins)
153.OL03 - Display / change LDK33 (stock)
154.OL04 - Display / change RLBES (stock)
155.OL05 - Display / change LDK30 (mat.whse)
156.OL06 - Display / change LDK31 (mat.type)
157.OL07 - Data transfer stor.bins LDK34->RLPLA
158.OL08 - Data transfer stor.bins RLPLA->B.I.
159.OL09 - Data transfer stor.bins LDK34->LAGP
160.OL10 - Test storage bin data transfer
161.OL11 - Data transfer stock LDK33->RLBES
162.OL12 - Data transfer stock RLBES-> B.I.
163.OL13 - Data transfer stock LDK33->LQUA
164.OL14 - Test stock data transfer
165.OL15 - Data transfer material whse no.view
166.OL16 - Test mat.master data transfer (MLGN)
167.OL17 - Data transfer material storage type
168.OL18 - Test mat.master data transfer (MLGT)
169.OLVS C SD Menu for Master Data
170.VM01 - Create Hazardous Material
171.VM02 - Change Hazardous Material
172.VM03 - Display Hazardous Material
WM-DWM
Decentralized Warehouse Management
1.DZ00 - Introduction to Decentralized Systems
2.LD01 - Repost Communication Document
3.LD02 - Reposting multiple comm.records
4.LD03 - Display Communication Document
5.LD04 - Evaluation of Communication Doc
6.LD05 - Check LDK01 Records (internal call)
7.LD06 - Check LDK02 Records
8.LD07 - Check LDK03 Records
9.LD08 - Check LDK04 Records (internal call)
10.LD09 - Check LDK05 records
11.LN07 - Number Ranges for WM Communic.Rec.

How to find Transaction code from Report/program name ?

Dear all,
How to find Transaction code if i know Report/program name ?

Hi,
In se 38 when u open ur program,in the application toolbar u have a button beside the where-used list button as display object list.on clicking this button,a window will be opened at the left most corner for repository browser,in this u can find any tranasctions,fileds,screens,dictionary structures defined for the program.
if any transaction is created for the program u can find it under the transaction folder.
revert back for further queries.
Regards,
Sravanthi

How to Know Transaction Code from whcih the Document is Created?

Hi,
How to know which T Code is used to create documents. For few documents say material document (MBLNR), I can find the T code from MKPF table from which it is created as T Code field is available.
If the table doesn't contain a T Code field, then how to find the T Code from which document is created?
Regards,
Hari.

CDHDR, if change documents are written. DBTABLOG, if table logging is active.
Otherwise...some knowledge of the SAP application components required.
Thomas

Feching Eccn code and HTS code from GTS to ECC

Hi Gurus,
I am extending a standard delivery idoc (DELVRY05) for some of the header and items fields.
i have tried to pull them throgh the FM /SAPSLL/***_DOCS_SD0C_GET_R3 i have passed the sales order number, item number and VBTYP to this FM to pull the Eccn code and HTS code.but all the tables are containing the zero entries.
Please help me. i have to populate the ECCN code and HTS code at the item level in my EXTENDED (Z)DELVRY05 idoc.
I have the SO number POSNR and material with me in the program.

Hi All,
I am now fetching the ECCN code and HTS code as beow:
You need to write an RFC enabled function module in GTS system, and then call this FM from ECC6.0 passing the RFC destination with help of the FM: /SAPSLL/CD_ALE_RECEIVER_GET_R3.
Call the FM as below:
Coding in ECC 6.0.
data: lv_rfc_dest TYPE bdibapi_dest-rfc_dest.
clear : w_so.
 w_so-vbeln = w_e1edl24-vgbel." It can be the SO number or the delivery number which will be passed to the RFC ZFM to GTS to fetch the ECCN and HTS code.
 append w_so to t_so .
 clear: w_so.
 CALL FUNCTION '/SAPSLL/CD_ALE_RECEIVER_GET_R3'
 IMPORTING
 ev_rfc_dest = lv_rfc_dest.
 IF lv_rfc_dest IS NOT INITIAL.
 CALL FUNCTION 'ZS_HS_ECCN_SCHB_COPY'
 DESTINATION lv_rfc_dest
 EXPORTING
 PRVSY = <fs_lips>-matnr
 IMPORTING
 ECCN = lv_eccn
 HSCODE = lv_stawn
 TABLES
 REFNO = t_so
 EXCEPTIONS
 systen_error = 1
 connection_failure = 2.
Lv_eccn and Lv_Stawn contains the ECCN and HTS code.
Coding of the ZFM in GTS:
Note: tables parameter of FM RefNo is optional, where as the material number is mandatory parameter for the FM.
 FUNCTION ZS_HS_ECCN_SCHB_COPY.
*"*"Local Interface:
*" IMPORTING
*" VALUE(PRVSY) TYPE /SAPSLL/PRVSY
*" EXPORTING
*" VALUE(ECCN) TYPE /SAPSLL/CCNGN
*" VALUE(HSCODE) TYPE /SAPSLL/CCNGN
*" VALUE(SCHB) TYPE /SAPSLL/CCNGN
*" VALUE(RADIO) TYPE /SAPSLL/CCNGN
*" VALUE(RADIO_ECCN) TYPE /SAPSLL/CCNGN
*" VALUE(TEXT) TYPE /SAPSLL/TEXT60
*" TABLES
*" REFNO STRUCTURE /SAPSLL/API6800_DLN_LC_S OPTIONAL
 DATA:lv_prtyp TYPE /sapsll/prtyp VALUE '01'.
DATA: lv_rptdt TYPE /sapsll/rptdt.
DATA:lr_datab TYPE /sapsll/rptst_r_t,
 lr_datbi TYPE /sapsll/rptet_r_t.
TYPES : BEGIN OF s_pr,
 guid_pr TYPE /sapsll/guid_16,
 END OF s_pr.
DATA: w_pr TYPE s_pr.
DATA: t_pr TYPE STANDARD TABLE OF s_pr.
TYPES : BEGIN OF s_hscode,
 guid_ctsnum TYPE /sapsll/guid_16,
 stcts TYPE /sapsll/stcts,
 datbi TYPE /sapsll/rptet,
 datab TYPE /sapsll/rptst,
 END OF s_hscode.
TYPES : BEGIN OF s_corref,
 GUID_POBJ TYPE /SAPSLL/CORREF-GUID_POBJ,
 REFNO TYPE /SAPSLL/CORREF-REFNO ,
 end of s_corref.
TYPES: begin of s_cuit,
 GUID_CUHD TYPE /SAPSLL/CUIT-GUID_CUHD,
 GUID_PR TYPE /SAPSLL/CUIT-GUID_PR,
 CTYDP TYPE /SAPSLL/CUIT-CTYDP,
 end of s_cuit.
TYPES : BEGIN OF s_t606g,
 LGREG TYPE /SAPSLL/T606G-LGREG,
 GGLND TYPE /SAPSLL/T606G-GGLND,
 end of s_t606g.
TYPES : BEGIN OF s_TLEGSU ,
 LGREG TYPE /SAPSLL/TLEGSU-LGREG ,
 CTSEX TYPE /SAPSLL/TLEGSU-CTSEX,
 end of s_TLEGSU .
TYPES : BEGIN OF s_ctsnum,
 GUID_CTSNUM TYPE /SAPSLL/ctsnum-GUID_CTSNUM ,
 STCTS TYPE /SAPSLL/ctsnum-STCTS ,
 CCNGN TYPE /SAPSLL/ctsnum-CCNGN ,
END OF s_ctsnum.
DATA: w_hscode TYPE s_hscode.
DATA: t_hscode TYPE STANDARD TABLE OF s_hscode,
 t_corref TYPE STANDARD TABLE OF s_corref,
 t_cuit TYPE STANDARD TABLE OF s_cuit,
 t_t606g TYPE STANDARD TABLE OF s_t606g,
 t_tlegsu TYPE STANDARD TABLE OF s_tlegsu,
 t_ctsnum TYPE STANDARD TABLE OF s_ctsnum,
 w_ctsnum TYPE s_ctsnum,
 w_tlegsu TYPE s_tlegsu,
 w_cuit TYPE s_cuit,
 lv_refno TYPE /sapsll/corref-refno,
 t_refno type STANDARD TABLE OF /SAPSLL/API6800_DLN_LC_S,
 w_refno TYPE /SAPSLL/API6800_DLN_LC_S.
TYPES : BEGIN OF s_eccn,
 ccngn TYPE /sapsll/ccngn,
 guid_ctsnum TYPE /sapsll/guid_16,
 END OF s_eccn.
DATA: lv_pname TYPE sy-repid,
 t_ztuhcd1 type STANDARD TABLE OF ztuhcd1,
 w_ztuhcd1 type ztuhcd1.
CONSTANTS: c_eccn TYPE char7 VALUE 'ECCN',
 c_HSCODE TYPE char7 value 'HSCODE'.
DATA: w_eccn TYPE s_eccn.
DATA: t_eccn TYPE STANDARD TABLE OF s_eccn.
DATA: w_radio TYPE s_eccn.
DATA: t_radio TYPE STANDARD TABLE OF s_eccn.
DATA:w_text TYPE /sapsll/text60.
REFRESH: t_pr,t_hscode,t_eccn,t_radio,lr_datbi,lr_datab, t_cuit,t_t606g,t_tlegsu,t_ctsnum.
CLEAR: t_pr,t_hscode,t_eccn,w_radio,hscode,eccn,schb,lr_datbi,lr_datab,lv_rptdt,w_ctsnum,w_tlegsu.
GET TIME STAMP FIELD lv_rptdt.
*BREAK-POINT.
CALL FUNCTION '/SAPSLL/VALID_RANGES_PREPARE'
 EXPORTING
 iv_rptdt = lv_rptdt
 iv_option = 'LT'
 IMPORTING
 er_datab = lr_datab
 er_datbi = lr_datbi.
CALL FUNCTION 'CONVERSION_EXIT_SLLPR_INPUT'
 EXPORTING
 input = prvsy
 IMPORTING
 output = prvsy.
SELECT guid_pr
 INTO TABLE t_pr
 FROM /sapsll/pntpr
 WHERE grvsy = 'LSG_ECC'
 AND prvsy = prvsy
 AND prtyp = lv_prtyp.
if refno[] is initial.
 IF NOT t_pr[] IS INITIAL.
 SELECT guid_ctsnum
 stcts
 datbi
 datab
 INTO TABLE t_hscode
 FROM /sapsll/prcts
 FOR ALL ENTRIES IN t_pr
 WHERE guid_pr = t_pr-guid_pr
 AND stcts IN ('US_HTS','EARECCN','US_SCHB','NRC_SCHB', 'NRCECCN')
 AND datbi IN lr_datbi[]
 AND datab IN lr_datab[].
ENDIF.
IF NOT t_hscode[] IS INITIAL.
 SELECT ccngn
 guid_ctsnum
 INTO TABLE t_eccn
 FROM /sapsll/ctsnum
 FOR ALL ENTRIES IN t_hscode
 WHERE guid_ctsnum = t_hscode-guid_ctsnum.
ENDIF.
LOOP AT t_eccn INTO w_eccn.
 READ TABLE t_hscode INTO w_hscode WITH KEY guid_ctsnum = w_eccn-guid_ctsnum.
 IF sy-subrc = 0.
 IF w_hscode-stcts = 'US_HTS'.
 hscode = w_eccn-ccngn.
 ELSEIF w_hscode-stcts = 'EARECCN'.
 eccn = w_eccn-ccngn.
 ELSEIF w_hscode-stcts = 'US_SCHB'.
 schb = w_eccn-ccngn.
 ELSEIF w_hscode-stcts = 'NRC_SCHB'.
 radio = w_eccn-ccngn.
 ELSEIF w_hscode-stcts = 'NRCECCN'.
 radio_eccn = w_eccn-ccngn.
 ENDIF.
 IF NOT radio IS INITIAL OR
 NOT radio_eccn IS INITIAL .
 SELECT SINGLE text
 INTO w_text
 FROM /sapsll/ctsnumt
 WHERE guid_ctsnum = w_hscode-guid_ctsnum
 AND ctstt = 'F'
 AND langu = 'EN'.
 IF sy-subrc = 0.
 text = w_text.
 ENDIF.
 ENDIF.
 ENDIF.
ENDLOOP.
Else.
IF NOT t_pr[] IS INITIAL.
 SELECT guid_ctsnum
 stcts
 datbi
 datab
 INTO TABLE t_hscode
 FROM /sapsll/prcts
 FOR ALL ENTRIES IN t_pr
 WHERE guid_pr = t_pr-guid_pr
 AND datbi IN lr_datbi[]
 AND datab IN lr_datab[].
endif.
read table refno into w_refno index 1.
if sy-subrc eq 0.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = w_refno-refno
 IMPORTING
 OUTPUT = lv_refno.
endif.
select GUID_POBJ
 REFNO
 from /sapsll/corref into TABLE t_corref
 where REFNO = lv_REFNO.
if t_corref is not initial.
select GUID_CUHD
 GUID_PR
 CTYDP
 from /sapsll/cuit into table t_cuit
 for all entries in t_corref
 where GUID_CUHD = t_corref-GUID_POBJ.
 endif.
if t_cuit is not initial .
select LGREG GGLND from /SAPSLL/T606G
 into table t_T606G
 for all entries in t_cuit
 where GGLND = t_cuit-CTYDP.
endif.
if t_T606G is not initial.
select LGREG
 CTSEX from /SAPSLL/TLEGSU
 into TABLE t_TLEGSU
 FOR ALL ENTRIES IN t_T606G
 where LGREG = t_T606G-LGREG.
endif.
if t_hscode[] is not INITIAL.
select GUID_CTSNUM
 STCTS
 CCNGN
 from /SAPSLL/CTSNUM
 into TABLE t_CTSNUM FOR ALL ENTRIES IN t_hscode
 where GUID_CTSNUM = t_hscode-GUID_CTSNUM .
endif.
REFRESH: t_ztuhcd1.
CLEAR: t_ztuhcd1,w_ztuhcd1.
* loop at t_TLEGSU into w_TLEGSU.
READ TABLE t_cuit INTO w_cuit index 1.
lv_pname = sy-repid.
* To retrive all the hard coded values
w_ztuhcd1-name = c_eccn.
* w_ztuhcd1-field = c_eccn.
w_ztuhcd1-zkey = w_cuit-ctydp.
APPEND w_ztuhcd1 TO t_ztuhcd1.
CLEAR: w_ztuhcd1,lv_pname.
* To retrive all the hard coded values
CALL FUNCTION 'Z_UHARD_CODE_VALUE'
 TABLES
 t_ztuhcd1 = t_ztuhcd1
 EXCEPTIONS
 no_data_found = 1
 OTHERS = 2.
if sy-subrc eq 0.
loop at t_ztuhcd1 into w_ztuhcd1 .
read table t_CTSNUM into w_CTSNUM with key STCTS = w_ztuhcd1-low.
if sy-subrc eq 0.
 eccn = w_CTSNUM-CCNGN.
endif.
endloop.
endif.
REFRESH: t_ztuhcd1.
CLEAR: t_ztuhcd1,w_ztuhcd1.
* lv_pname = sy-repid.
* To retrive all the hard coded values
w_ztuhcd1-name = c_HSCODE.
* w_ztuhcd1-field = c_HSCODE.
w_ztuhcd1-zkey = w_cuit-ctydp.
APPEND w_ztuhcd1 TO t_ztuhcd1.
CLEAR w_ztuhcd1.
* To retrive all the hard coded values
CALL FUNCTION 'Z_UHARD_CODE_VALUE'
 TABLES
 t_ztuhcd1 = t_ztuhcd1
 EXCEPTIONS
 no_data_found = 1
 OTHERS = 2.
if sy-subrc eq 0.
loop at t_ztuhcd1 into w_ztuhcd1 .
read table t_CTSNUM into w_CTSNUM with key STCTS = w_ztuhcd1-low.
if sy-subrc eq 0.
 HSCODE = w_CTSNUM-CCNGN.
endif.
endloop.
endif.
endif.
ENDFUNCTION.

Problem with calling we02 transaction code from web dynpro

Hello everyone,
I want to skip the initial screen of we02 tcode for this i have created the URL, provided the idoc number and
used the function code DYNP_CODE=ONLI for execute button.
DATA : FINAL_URL TYPE STRING.
CONCATENATE 'host' '.port' '/sap/bc/gui/sap/its/webgui?~transaction=we02 DOCNUM-LOW='
ls_itab-docnum ';CREDAT-low=' ' ' ';DYNP_OKCODE=ONLI'
into FINAL_URL.
I am trying to pass the idoc number internally and click on execute button...so that the end user can see the idoc display directly, rather than clicking the execute button manually. But, unfortunately the function code for execute buttong (ONLI) is not working. In WE02 tcode, provided input values are appeaing correctly but not triggering the execute button.
Please help!
Thanks in advance...

Hi Rohit.,
Did u tried my previous reply., Use., & ~OKCODE=ONLI .,
http://host:8000/sap/bc/gui/sap/its/webgui?sap-system-login-basic_auth=X&sap-client=800&sap-language=EN&transaction=we02&okcode=ONLI
tis will work.,
Thanks & Regards
Kiran

Trigger T-Code Synchronously from WD4A

Hi All,
I have a requirment in which I have to trigger a transaction code from WD4A view synchronously.
After the transaction code is opened in another window the WD4A component should continue to listen if the transaction code window is closed.
e.g.. when a confirmation pop-up window is displayed in WD4A the control is gained by the pop-up window and user cannot perform any action on the parent or main window. And when the pop-up closes the parent window gets to know this. The parent view is again rendered.
In a similar way i have to trigger a transaction from WD4A.
The parent View/Window should be inactive till the transactional window is open and the parent window/view should listen when the transaction window is closed.
Please let me know how this can be done.
Can this be achieved by transactional i-View or any other method.
Regards,
Sameer.

Hi Sameer,
Thomas is right - I think always right :-).
However you might want to consider not holding both sessions (WDA and GUI) open.
You have not supplied enough detail but this concept may work.
1. You could launch a GUI (HTML or Windows) from your WDA.
If you want to do the Windows version, then you can attach a shortcut file to the frontend (ie like a PDF or pic file). Depending on SSO, Windows File Types (.sap), browser setting etc you can get the Windows GUI to open on the transaction you want. We have done this.
2. Then close the WDA window after opening the transaction (Exit Plug).
3. On closing the transaction, trigger the WDA again (maybe an exit on save or a wrapper for the transaction).
Saying all that, without further info, you might be needing to pass parameters into the WDA to manage the flow.
In addition; if searching etc was used up front, you may be needing to save these off before calling the transaction, then using them on the way back.
All this depends on how keen you are to manage this.
Personally, I would stick with Thomas's answer.
JS

From program to know the transaction code

Hi all,
How to see/know the transaction code from SE38? or any other methods to know if we know only program name not known t.code?
early reply highly appriciated/awarded.
Soma

Hi Soma:
Refer to this website
http://www.easymarketplace.de/transactions.php
Please let me know if you need more information.
Assign points if useful.
Regards
MSReddy

Fi validation -exclude tr code from other modules

I am setting up a validation at the Fi line item level. Now it is restricting some documents comming from MM which we don't want to. Is it possible to exclude some of the transaction codes from other modules to not to consider this validation.
I tried SYST-TCODE <> (T-Code from other modules like MM for eg: MIRO etc)
But that does not seem to work.
Does anyone know why and are there any options to get this done.
Any help will be appreciated

Hello,
Please validate BKPF-AWTYP (reference procedure)
For postings done in FI its, BKPF and so for others it would change.
This would be simple.
But for this check whether this field can be used for validation.
This can be done by checking table GB01, if not change the settings to make this field available for validation.
Best Regards
Anantha

How to create Transaction code for ABAP and execution by other user

Hi All,
Could someone please let me know how to create transaction code in detail for ABAP program. Step by step procedure expected. I would like to know how other user can execute the report using same transaction code which I have created.
More about authorization.
Thanks in advance.

Hello,
You can create transaction code from se80 as well.In object navigator,right click on your program name and create->transaction code.You can create transaction and select if it is only a report,a report with selection-screen depending on your requirement.You can run your report directly by entering the transaction code in the command field.
You can authorise the users who can use your transaction:
Authorisation objects are used to restrict certain transactions to users.Critical data must be protected from unauthorised users.For example,the head has access to certain data.But it cannot be accessed by his subordinate.For this we need to define roles.
Create an authorization object with transaction SU21.
An object usually consists of the ACTVT (activity) field and one other field,which specifies the data type to be protected.By ACTVT, we can decide if the data is accessible for change,display only etc.
Add authorization fields to the authorization object created.
Assign the authorization object to the transaction using SE93.
Attach the authorization object to the role using transaction PFCG.
If you want to assign roles,use transaction PFCG.Create a new role.In the AUTHORIZATIONS tab,you can get a self generated profile name and a profile text by clicking on the icon next to it.Then go to the "Change Authorization data" and choose an authorization template.Then you can choose to display/change/create an activity and after the selection,click on the red and white circle.The profile will now be created.
In the user tab,you can give the user details who can use this role.
Also check this link:
http://www.*********************/r3_security/r3_security_tips.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/52/6716a6439b11d1896f0000e8322d00/content.htm
Very helpful guide:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a92195a9-0b01-0010-909c-f330ea4a585c
Regards,
Beejal
**Reward if answer is helpful

Cannot trace the transaction code within a role

Hello All,
We, in our project trying to trace out various transaction codes assigned to each of roles.
I have an issue tracing an transaction code FB60. When i searched in suim for transaction codes within the role, I could see FB60 listing in the results.
But when i go to role through pfcg and see in the menu tab i cannot find the transaction code there.
what went wrong here? Now i want to remove the transaction code from the role so that next time when i use suim it wont be listed in the results.
Kindly advice.
Regards,
Brahmeshwar Poloju

HERE IS THE OUTPUT.
OBJECT     AUTH         VARIANT FIELD      LOW                                      HIGH
S_TCODE    T-DC84003900         TCD        SCPE*
S_TCODE    T-DC84003900         TCD        SDD1*                                    SE03
S_TCODE    T-DC84003900         TCD        SE07                                     SE16N
S_TCODE    T-DC84003900         TCD        SE17                                     SECQ*
S_TCODE    T-DC84003900         TCD        SEEF*                                    SI24_12
S_TCODE    T-DC84003900         TCD        SI2414                                   SIBU
S_TCODE    T-DC84003900         TCD        SIC_*                                    SLAT
S_TCODE    T-DC84003900         TCD        SLG0                                     SLIB_*
S_TCODE    T-DC84003900         TCD        SLIN                                     SLXT
S_TCODE    T-DC84003900         TCD        SM30
S_TCODE    T-DC84003900         TCD        SM31                                     SM37
S_TCODE    T-DC84003900         TCD        SM50
S_TCODE    T-DC84003900         TCD        SM51
S_TCODE    T-DC84003900         TCD        SMAR*                                    SMEZ
S_TCODE    T-DC84003900         TCD        SMTH*                                    SNLS
S_TCODE    T-DC84003900         TCD        SNRO                                     SO99
S_TCODE    T-DC84003900         TCD        SOACARRY*                                SOTR*
S_TCODE    T-DC84003900         TCD        SP02
S_TCODE    T-DC84003900         TCD        SCUS*                                    SDCA*
S_TCODE    T-DC84003900         TCD        /*                                       DA_*
S_TCODE    T-DC84003900         TCD        DC*                                      PFCF*
S_TCODE    T-DC84003900         TCD        PFD*                                     RYZ*
S_TCODE    T-DC84003900         TCD        RZZ*                                     SAIM*
S_TCODE    T-DC84003900         TCD        SAIO*                                    SAK*
S_TCODE    T-DC84003900         TCD        SAM*                                     SAPTE*
S_TCODE    T-DC84003900         TCD        SARJZ*                                   SARTN*
S_TCODE    T-DC84003900         TCD        SASAPCATT                                SBEA
S_TCODE    T-DC84003900         TCD        SBI*                                     SC2_*
S_TCODE    T-DC84003900         TCD        SCA*                                     SCBZ*
S_TCODE    T-DC84003900         TCD        SCDO                                     SCI*
S_TCODE    T-DC84003900         TCD        SCTS*                                    SCU3
S_TCODE    T-DC84003900         TCD        SWF_TR*                                  SYNT
S_TCODE    T-DC84003900         TCD        SZG*                                     TRBS
S_TCODE    T-DC84003900         TCD        TRCM*                                    UR_M*
S_TCODE    T-DC84003900         TCD        USRM*                                    _Z*
S_TCODE    T-DC84003900         TCD        SWF_CN*                                  SWF_RE
S_TCODE    T-DC84003900         TCD        SPEC*                                    SPERS*
S_TCODE    T-DC84003900         TCD        SPP*                                     SPROJE
S_TCODE    T-DC84003900         TCD        SQ00                                     SRT*
S_TCODE    T-DC84003900         TCD        SSC                                      SSDZ*
S_TCODE    T-DC84003900         TCD        SST0                                     ST05*
S_TCODE    T-DC84003900         TCD        ST14                                     ST62
S_TCODE    T-DC84003900         TCD        STCU                                     STKZ*
S_TCODE    T-DC84003900         TCD        SV*                                      SWF_BA
S_TCODE    T-DC84003900         TCD        SURAD                                    SURVEY
S_TCODE    T-DC84003900         TCD        SU50                                     SU52
S_TCODE    T-DC84003900         TCD        SU3
S_TCODE    T-DC84003900         TCD        SU2
S_TCODE    T-DC84003900         TCD        SU0
S_TCODE    T-DC84003900         TCD        STS*                                     STYLE*
Regards

Trigger Transaction code from BW to ECC

Similar Messages

Maybe you are looking for