NWA RFC Destinations Mass Maintenance (creation, exporting, ...)
Hello,
I would like to be able to maintain a number of RFC Destination on different landscapes without having to create them manually on each server. Ex. I have 10 RFC (or other type) Destinations. I have 50 servers. I want to be able to duplicate the destinations by one of the following ways:
1- Export the destinations from one machine, and upload them to the others;
2- Maintain the destinations in a resource file, copy this file to the other machines, trigger a script that would create those destinations in my other machines NWA.
To my knowledge there is no standard feature in NWA that allows copying/exporting of RFC destinations.
Any suggestions?
Thanks!
I don't think is possible, I think you'll have to do this manually unfortunately.
Regards
Juan
Similar Messages
-
Creation of New T-Code for mass maintenance of SA
SAP currently does not have a facility to mass-maintain schedule agreements. The business alone has over 16,000 schedule agreement lines. Manual maintenance is very time consuming.
There are some key items of data that can require amendent for a particular vendor. The new program would permit the maintenance of:
Planned delivery time EKPO-PLIFZ
GR proc Time EKPO-WEBAZ
Firm Zone EKPO-ETFZ1
Trade off Zone EKPO-ETFZ2
Binding Grp EKPO-KZSTU
Conf Control Key EKPO-BSTAE
Vendor Material number EKPO-IDNLF
Stock type EKPO-INSMK
Creation profile EKPO-ABUEB
approach from my functional consultant:
basically i want to update the fileds on a screen of tcode : memasspo (mass maintenance of purchase orders )
if i select pur ord item in the initial screen,
it allows me to enter pur doc values and item values
after that
if i select fields symbol button on left side
and i can select fields which i have to be updated in the right side in the Popup screen
if i choose fields they will come along with pur doc and item in the screen
My question is :
pur doc and item values with additional fields data is available in the flat file that should be updated
pl let me know the approach to upload whether i go for eigther BDC or BAPI
Note :
i can update for newly added fields in the user defined SAP Screen itself for porders
but if i enter the purchasing doc as scheduling agreement no it wont allow you to update
i need to update for Scheduling agreements ?
<removed_by_moderator>
Thanks in advance
Edited by: Julius Bussche on Sep 3, 2008 9:56 AMHi Hariprasad,
If restricting certain fields using field selection option is not suitable for you, you can go ahead with the option Screen Variend
Also refer the link
[https://wiki.sdn.sap.com/wiki/display/Snippets/Transaction%20Variant%20-%20A%20Step%20by%20Step%20Guide%20for%20Creation] -
Hi All,
Can anyone tell me if I can export all my RFC destination information in a transport request or other form ?
Regards
LauranHi,
You cannot transport RFC Destinations directly. But there is a way,
Create a new Transport Request. After you have created the transport click on the request and in menu choose Request/Task and then Display. Goto change mode.
In PGMID give the value R3TR
In Obj give value TABU
In Object Name give RFCDES.
After that double click on table name entry. You will come to the screen: Transport organizer:Change Key List.
Here choose insert line. A new line with table name and key as the column headers will come up.
Double click on the Bobject Field. In the next screen you will get options to fill in the key.
You can insert key as per your choice. If you want to transport all the RFC Destinations give '*'. If you want to transport a RFC Des called say 'ABC' give the key as 'ABC'.
Release the transport and import it in the target system. -
Export or transport all the RFC destination from one system to another syst
Hi
Is there any method to Export or transport all the RFC destination from one system to another systemHi,
the information is stored in table rfcdes.But there are also some other RFC*-tables which have some relations. Nevertheless the RFC-connectons will possibly not work anymore in the new system(depending on the release your systems are), as the passwords are stored in the Sec store with system-dependent keys.
b.rgds, Bernhard -
SSL certificates not visible while RFC destination creation
Hi all,
I am setting up an RFC destination to connect to external server and which uses SSL certificates for its authorization.
So i have imported the Client certificates into STRUST.
While setting up an RFC connection of type G, in the security tab when we select the SSL security certificate radio button, will we be able to see the certificates(in the combo box) that we have imported in STRUST.
Currently, though i have imported the Client certificates into STRUST, i am not able to see them in the SS security certificates combo box.
Kindly help me out.
Cheers,
Siva Maranani.Well, first of all we should avoid confusion by using the term "<i>ABAP destination</i>" rather than "<i>RFC destination</i>" (although ABAP transaction SM59 still has this old title).
When referring to an "ABAP destination of type G" we are talking of an outbound http connection to a non-ABAP server (e.g. an SAP J2EE server or any other http server).
I'm not sure whether you are aware that in this context "<i>SSL client certificate</i>" refers to the ABAP <u>system</u> (which is the SSL client in this scenario). This is different from scenarios where "X.509 client certificate" refers to a certificate which is assigned to an individual <u>user</u> (using a web browser). <b>In the given scenarios, where two systems are the communication peers, SSL cannot be used for user authentication.</b> That fact is often misunderstood.
By default you'll find 3 different SSL certificates (actually: PSEs) in an ABAP system (which can be used only after enabling SSL, of course - see note 510007 for instructions):
- SSL Server
- SSL Client (anonymous)
- SSL Client (Default)
Well, the "<i>SSL Client (anonymous)</i>" is actually not really a "client certificate" but used for outgoing http requests where you do not intend to send your own SSL client certificate. Since you cannot use the server's SSL client certificates for user authentication it might make sense to use "<i>SSL Client (anonymous)</i>" is most cases.
Please notice: you have to add the server's SSL certificate (respectively the root CA certificate and potentially intermediate CA certificates) to the certificate list of the "<i>SSL Client (anonymous)</i>" PSE (using STRUST). By default, that list is empty - consequently no SSL server certificate is trusted (in contrast to a web browser which is already shipped with a long list of "trusted CAs").
Only when the (remote) server demands SSL client certificates it might make sense to use either "<i>SSL Client (Default)</i>" or to define a new SSL client certificate (for the ABAP system that submits the https request).
Please notice:
SSL client certificates need to be issued by an Certification Authority (CA) in order to be accepted by the SSL server.
In addition to importing the SSL server's certificate to the certificate list of the SSL client PSE (see above: <i>anonymous SSL client</i>) you also need to export the root CA certificate (and potentially all intermediate CA certificates) of the SSL client certificate and import it to the (remote) SSL server's keystore (kindly refer to the manuals of that server for instructions).
Kind regards, Wolfgang
PS: I assume that you have imported some certificates to the certificate list of a SSL client PSE. In SM59 only those SSL client PSEs are listed: "<i>SSL Client (anonymous)</i>", "<i>SSL Client (Default)</i>" and all SSL client PSEs that you might have defined in addition (using transaction STRUST => <i>Environment</i> => <i>SSL Client Identities</i>). -
Creation of RFC destination for SAP-Access Connectivity
Hi,
I want to create a RFC destination for SAP-Access connectivity.
Can I get some help regarding it's connection type,activation type and gateway options required for the same.
Regrads,
Anthony D'souzaHi
Please see the following:
1. Create an entry in Trxn DBCA for SQL Server in SAP, you are creating a database connection for the SQL server in SAP.
2. You use this connection, and write Native SQL stmnts...between EXECSQL...ENDEXEC to fetch the data..and then normal ABAP statements to put that data into your ztable.
TABLE DBCON Entry can be like this...depends on your External database..
CON_NAME Raj Logical name for connection
DBMS MSS Microsoft SQL Server
USER_NAME <User name> For SQL Server
PASSWORD <password> " "
CON_ENV MSSQL_SERVER=<server> MSSQL_DBNAME=<database name>
DB_RECO Availability type for an open database connect
FUNCTION z_houston_connect.
""Local interface:
EXEC SQL.
CONNECT TO 'RAJ' AS 'V'
ENDEXEC.
EXEC SQL.
SET CONNECTION 'V'
ENDEXEC.
*- Get the data from MS-SQL Server
EXEC SQL.
open C1 for
select
l.loc_id,
l.loc_name,
a.acc_id,
a.acc_name,
d.person
from ho_loc_mast as l
inner join snd_acc_mast as a on l.loc_id = a.loc_id
inner join snd_acc_addr as d on a.loc_id = d.loc_id and
a.acc_id = d.acc_id
where l.loc_id = '001'
ENDEXEC.
DO.
EXEC SQL.
FETCH NEXT C1 into :wa-c_locid, :wa-c_locname, :wa-c_acc_id, :wa-c_acc_name, :wa-c_person
ENDEXEC.
IF sy-subrc = 0.
PERFORM loop_output.
ELSE.
EXIT.
ENDIF.
ENDDO.
EXEC SQL.
CLOSE C1
ENDEXEC.
ENDFUNCTION.
Regards,
Raj -
Creation of RFC Destination for Syncronouse RFC adapter.
Hi,
Can any one please give me step by step process to create RFC destination in XI and SAP-R3. plz help me out
thanks,
dhanush.No one is going to help you if you keep posting same question multiple times.
You need to priovide more details on what you are doing ? There are many reasons why you create a RFC destination in XI and R3. There are multiple types of RFC destinations. What is the end to end scenario you want to implement. It all depends on this. Try to provide more details.
Regards
Bhavesh -
Creation of RFC Destination problem
Hi Experts,
I need to establish an RFC communication between TREX7.0 server running on windows 2003 server and the SAPR/3 4.7 EE server running on windows2000.
server. Initially i used TREXAdminTool to create RFC Destination, i was unable to create successfully
Then i used SAPR/3 server from TCODE: SM59, here also am facing the same problem, what are the values i have to give for
1. RFC Destination, 2. Program id 3. Gateway Host and Gateway Service.
PLZ guide me step by step procedure with some example values to create RFC Destination to TREX Server successfully using TREXAdminTool or from SAPR/3 server---SM59
ADV Thanks
Regds
phanikumarHi,
Till now i didn't install explicitly any SAP Gateway on TREX server.
I installed TREX server along with SAP Netweaver WEB AS java.
Shall i need to install any SAP Gateway to configure RFC Destination?
If so can you give me the procedure how to install explicitly SAP gateway?
Regds
Phanikumar -
RFC destination of receiver system
Hi Guys,
I am trying to do the shell creation from scracth, and now i have found on the RFC destination creation there are three RFC connection which needs to be define. But my question is in this step we dont have any receiver system becasue export files has not been generated yet that will come after this step, so how can i proceed.
Regards,
SubhashHello Subhash,
In the step 'Define RFC Destinations' you create the RFC destinations for the SAP systems that participate in your project (or subproject).
Yes, you are correct, since the target/receiver system is not yet created, you cannot establish a RFC for the same.
Please proceed by maintaining the following:
Server name, System number , Language, Client, Username and Password for the control and the sender system.
Best Regards,
Mridu. -
Mass Maintenance of EDI Partner Profiles
Hello SDN folks,
my customer is a large multinational - and they are beginning to run into difficulties in the management of their EDI partner profiles. The problem is that there are thousands of external parties that must be communicated to via IDOC / the outbound EDI processing technique. Very many of these partner profiles are very similar / identical to each other. My customer needs to have seperate profiles though so that the messages can be fully traced from point of sending to destination and so that they can easily start and stop communications for a specific partner if required.
The question I have is - are there any good tools for the mass maintenance of EDI profiles for customers that are in our situation? It occurs to me that this must be a common problem for many large organisations. It would be convenient to be able to mass maintain shared EDI partner profiles (profiles that share common attributes). There does not appear to be any solution provided in standard SAP (except for some ECATT utility for mass creation - that cannot be used in production). Does anyone know of a SAP standard solution - or even a third party solution for this problem?
Kind Regards,
Julian PhillipsHi Julian
I also ran into this issue. Check function group EDI6, there are some function modules your ABAP'ers might be able to leverage to do the mass maintenance. The other option is use of BDC sessions.
Im trying to find something similar to mass create logical systems in tcode SALE which is a prereq if you plan on mass loading LS's in WE20.
Good luck.... -
Hi Experts,
I am doing User Exit for MIGO.
I have done it successfully.but problem comes when the email is sent to the vendor, MIGO is getting DUMP.
So, to cross check i have remove the User Exit of MIGO. but to my surprise when i press POST button in MIGO the similiar DUMP comes.
So wht is the solution for this.
For your Information DUMP message is:
Runtime Errors MESSAGE_TYPE_X
Date and Time 06.12.2007 14:57:55
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
No RFC destination is defined for SAP Global Trade Services
Long text of error message:
Technical information about the message:
Message class....... "/SAPSLL/PLUGINR3"
Number.............. 002
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMBWL" or "LMBWLU21"
"MB_POST_GOODS_MOVEMENT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "vngsap1"
Network address...... "192.168.0.10"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "VNGSAP1"
Database type..... "MSSQL"
Database name..... "EC6"
Database user ID.. "ec6"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 20 2007 00:45:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 102
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 21953056
Heap.... 0
Page.... 73728
MM Used. 15443024
MM Free. 1280936
User and Transaction
Client.............. 800
User................ "VEDHRUV"
Language key........ "E"
Transaction......... "MIGO "
Transactions ID..... " "
Program............. "SAPLMBWL"
Screen.............. "SAPLMIGO 0001"
Screen line......... 18
Information on where terminated
Termination occurred in the ABAP program "SAPLMBWL" - in
"MB_POST_GOODS_MOVEMENT".
The main program was "SAPLMIGO ".
In the source code you have the termination point in line 59
of the (Include) program "LMBWLU21".
Source Code Extract
Line
SourceCde
29
when a goods movement for an inbound or outbound delivery is posted
30
directly from VL31N/ VL01N, XBLNR is not yet known when we call
31
CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
32
BKPF as well. There is no other way to forward XBLNR to FI as not
33
every document is posted by MB_CREATE -> a new function module in
34
MBWL for transferring the information, called by FI, meant to load
35
the complete function group for all MBxx postings when this isn't
36
required (Performance). Would be the better way to transport the
37
information after switching off MBxx in later release.
38
corresponding IMPORT ... FROM MEMORY ... can be found in
39
AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40
l_mem_id = 'MKPF-XBLNR'. " 641365
41
EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365
42
ENDIF.
43
IF xmkpf-xabln IS INITIAL. "note 434093
44
CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093
45
ENDIF. "note 434093
46
47
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50
CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51
EXCEPTIONS
52
error_message = 4.
53
As soon as we have started to put things into UPDATE TASK, we must
54
ensure that errors definitely terminate the transaction.
55
MESSAGE A is not sufficient because it can be catched from
56
external callers which COMMIT WORK afterwards, resulting in
57
incomplete updates. Read note 385830 for the full story.
58
IF NOT sy-subrc IS INITIAL.
>>>>>
MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
60
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61
MESSAGE A263.
62
ENDIF.
63
Optische Archivierung
64
Spaete Erfassung mit Barcode
65
Redesign of barcode handling -> note 780365
66
PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67
xmkpf-mjahr
68
barcode.
69
70
MOVE-CORRESPONDING xmkpf TO emkpf.
71
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72
EXCEPTIONS
73
error_message = 4.
74
MOVE-CORRESPONDING xmkpf TO emkpf.
75
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76
EXCEPTIONS
77
error_message = 4.
78
IF NOT sy-subrc IS INITIAL.
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
MIGO_STATUS
SY-UCOMM
OK_POST1
SY-TITLE
Goods Receipt Purchase Order 4500017132 - shah
SY-MSGTY
X
SY-MSGID
/SAPSLL/PLUGINR3
SY-MSGNO
002
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071206
SY-UZEIT
145755
SY-XPROG
SAPLBPFC
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
7 FUNCTION SAPLMBWL LMBWLU21 59
MB_POST_GOODS_MOVEMENT
6 METHOD SAPLMIGO LMIGOKG1 921
LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
5 METHOD SAPLMIGO LMIGOKD1 309
LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
4 METHOD SAPLMIGO LMIGOKD1 9
LCL_MIGO_KERNEL=>DOCUMENT_POST
3 METHOD SAPLMIGO LMIGOST2 124
LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER
2 METHOD SAPLMIGO LMIGOFR2 172
LCL_MIGO_FRAME=>OKCODE_DISPATCH
1 MODULE (PAI) SAPLMIGO LMIGOPAI 11
PAI_OKCODE_DISPATCH
Chosen variables
Name
Val.
No. 7 Ty. FUNCTION
Name MB_POST_GOODS_MOVEMENT
XBLNR_SD
2222
0000
0000
0000
EMKPF
000000000000000000 ##
2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMSSA[]
Table IT_3831[0x196]
FUNCTION-POOL=MBWLDATA=XMSSA[]
Table reference: 396
TABH+ 0(20) = 0000000088F26C31000000008C010000F70E0000
TABH+ 20(20) = 00000000C4000000FFFFFFFF04E90400E01B0000
TABH+ 40( 8) = 08000000C1108001
store = 0x00000000
ext1 = 0x88F26C31
shmId = 0 (0x00000000)
id = 396 (0x8C010000)
label = 3831 (0xF70E0000)
fill = 0 (0x00000000)
leng = 196 (0xC4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000134
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x40F26C31
>>>>> 2nd level extension part <<<<<
tabhBack = 0xA0F5EA30
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
RRESWK
22222222222
00000000000
00000000000
00000000000
%_SPACE
2
0
0
0
L_MEM_ID
2222222222
0000000000
0000000000
0000000000
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMSPR_KEY
00000000
222222222222222222222222222222222222233333333
000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000
SCREEN
GODYNPRO-DETAIL_TAKE
4445455424454445544422222222222222222222222222222222222222222222222222222222222222222222222222
7F49E02FD45419CF41B500000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IT_RSTRUCT
Table[initial]
XMKPF-XABLN
2222222222
0000000000
0000000000
0000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLMBWL
5454445422222222222222222222222222222222
310CD27C00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ODM07M[]
Table[initial]
GT_GOCOMP
000000000000 #### 00000000000000
3333333333332222222222222222222222222222222222222222222220000222222222222223333333333333322222
000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
4
0000
4000
L_ATPCB
22222
00000
00000
00000
XMKPF-MBLNR
5000011865
3333333333
5000011865
0000000000
0000000000
XMKPF-MJAHR
2007
3333
2007
0000
0000
BARCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T003
800WE50AMS X XX XXXXXH
3335433445222222222522222222222222225522555554222222
80075501D3000000000800000000000000008800888888000000
0000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000
KNVV
00000000 000
2222222222222222222222222222222223333333322222222222222222222233322222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T064B
2222222222222222222222
0000000000000000000000
0000000000000000000000
0000000000000000000000
VGMSEG[]
Table[initial]
No. 6 Ty. METHOD
Name LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
ES_EMKPF_OLD
5000011865200700000000000000 ##
3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_EMKPF
000000000000000000 ##
2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OREF_TITLEBAR
|
| E0001000 |
| 60009000 |
| LS_EMKPF-SUBRC |
| 0 |
| 0000 |
| 0000 |
| C_MOD_ON |
| 1 |
| 3 |
| 1 |
| 0 |
| 0 |
| GOITEM-ERFMG |
| 0.0.0.0.0.0.1. |
| 0001000 |
| 000000C |
| LS_EMKPF-MBLNR |
| |
| 2222222222 |
| 0000000000 |
| 0000000000 |
| 0000000000 |
| SY-XPROG |
| SAPLBPFC |
| 5454454422222222222222222222222222222222 |
| 310C206300000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-REPID |
| SAPLMIGO |
| 5454444422222222222222222222222222222222 |
| 310CD97F00000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-MSGID |
| /SAPSLL/PLUGINR3 |
| 25455442545444532222 |
| F3103CCF0C579E230000 |
| 00000000000000000000 |
| 00000000000000000000 |
| TV_GODEFAULT_TRANSFER-CX |
| <initial> |
| <initial> |
| <initial> |
| SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| SY-MSGNO |
| 002 |
| 333 |
| 002 |
| 000 |
| 000 |
| SY-MSGV1 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ES_EMKPF_OLD-MSGV1 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV2 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV3 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| SY-MSGV4 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| GODEFAULT_TV |
| 101 GR goods receipt |
| 2222223332245266667276666772222 |
| 000000101007207FF43025359040000 |
| 0000000000000000000000000000000 |
| 0000000000000000000000000000000 |
| LS_EMKPF-MJAHR |
| 0000 |
| 3333 |
| 0000 |
| 0000 |
| 0000 |
| OREF_TIP |
|
D0002000
90006000
TV_GOSPLIT-CURRENT_LINE
<initial>
<initial>
<initial>
No. 5 Ty. METHOD
Name LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
I_SIMULATE
2
0
0
0
I_SIM_VALUES
2
0
0
0
I_ERROR_ONLY
2
0
0
0
E_OK
2
0
0
0
ET_XMSEG
Table[initial]
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
LS_EMKPF
5000011865200700000000000000 ##
3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LT_EMSEG
Table IT_4407[2x744]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_EMSEG
Table reference: 460
TABH+ 0(20) = F06C0731F83FE73000000000CC01000037110000
TABH+ 20(20) = 02000000E8020000FFFFFFFF0400000040420100
TABH+ 40( 8) = 10000000C1308001
store = 0xF06C0731
ext1 = 0xF83FE730
shmId = 0 (0x00000000)
id = 460 (0xCC010000)
label = 4407 (0x37110000)
fill = 2 (0x02000000)
leng = 744 (0xE8020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#001704
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xB8902E31
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 3425 (0x610D0000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0xE0D66931
>>>>> 2nd level extension part <<<<<
tabhBack = 0x00F11C31
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
LT_XMSEG
Table IT_4408[2x2364]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_XMSEG
Table reference: 464
TABH+ 0(20) = A0BEF93070D7693100000000D001000038110000
TABH+ 20(20) = 020000003C090000FFFFFFFF0400000030310100
TABH+ 40( 8) = 04000000C1308401
store = 0xA0BEF930
ext1 = 0x70D76931
shmId = 0 (0x00000000)
id = 464 (0xD0010000)
label = 4408 (0x38110000)
fill = 2 (0x02000000)
leng = 2364 (0x3C090000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#001613
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x28DF3031
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 3511 (0xB70D0000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x28D76931
>>>>> 2nd level extension part <<<<<
tabhBack = 0x90F4EA30
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
LT_IMSEG
Table IT_4396[2x2792]
FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_IMSEG
Table reference: 465
TABH+ 0(20) = D0D5693190D7693100000000D10100002C110000
TABH+ 20(20) = 02000000E80A0000FFFFFFFF04000000E0410100
TABH+ 40( 8) = 04000000C1308001
store = 0xD0D56931
ext1 = 0x90D76931
shmId = 0 (0x00000000)
id = 465 (0xD1010000)
label = 4396 (0x2C110000)
fill = 2 (0x02000000)
leng = 2792 (0xE80A0000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#001702
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xE01BC930
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 3413 (0x550D0000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0xC8626B31
collHook = 0x00000000
ext2 = 0x80626B31
>>>>> 2nd level extension part <<<<<
tabhBack = 0xD88C0331
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
LT_CANCEL
Table[initial]
ABAP_TRUE
X
5
8
0
0
LCL_MIGO_GLOBALS=>IF_BADI
|
| F0000000 |
| 70008000 |
| SYST |
| ######################################T##########################################ÿ##### C#### |
| 0000000000000000000000000000000000000050000000005000000000000000000000000000109000F00050240000 |
| 100010000000000000001000100010000000004000C0B0403000000000000000000000000000B00000F00080030400 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000 |
| 00000000000000000000000000000000000000000000000010000000000000000000000000000000000000D000000C |
| LS_XMKPF |
| 80050000118652007WEWEPR20071206200712062007120614575300000000VEDHRUV |
| 3333333333333333354545533333333333333333333333333333333333333544455522222222222222222222222222 |
| 8005000011865200775750220071206200712062007120614575300000000654825600000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| ME |
|
F0000000
D0002000
%_SPACE
2
0
0
0
L_NO_ITEMS
2
0
0
0
TV_GODEFAULT-CX
<initial>
<initial>
<initial>
LCL_MIGO_GLOBALS=>CALLER_SYTCODE
MIGO
44442222222222222222
D97F0000000000000000
00000000000000000000
00000000000000000000
LCL_MIGO_GLOBALS=>RETAIL_CONSIGNMENT_ACTIVE
2
0
0
0
%_FSREG_001
No. 4 Ty. METHOD
Name LCL_MIGO_KERNEL=>DOCUMENT_POST
E_OK
2
0
0
0
ME
|
| F0000000 |
| D0002000 |
| ABAP_FALSE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| LCL_MIGO_GLOBALS=>EXTERNAL_CALL_LEAVE_AFTER_POST |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 3 Ty. METHOD |
| Name LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER |
| I_OKCODE |
| OK_POST1 |
| 4455455322222222222222222222222222222222222222222222222222222222222222 |
| FBF0F34100000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000 |
| OREF_BADI_LOG |
|
D0002000
5000A000
%_FSREG_001
%_PRINT
000 0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LCL_MIGO_GLOBALS=>KERNEL
|
| F0000000 |
| D0002000 |
| %_VIASELSCR |
| # |
| 0 |
| 4 |
| OREF_DETAIL_BATCH |
|
60009000
0000F000
GOSEARCH_PO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 2 Ty. METHOD
Name LCL_MIGO_FRAME=>OKCODE_DISPATCH
I_OKCODE
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
L_MSG_STRING
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_OKCODE
OK_POST1
4455455322222222222222222222222222222222222222222222222222222222222222
FBF0F341000000000000000000000000000000000000000000000000000000000Hi Dhruv Shah,
Can you please tell me which user exit you are using for doing that. coz i am in need of that.
Thanks,
Ajeeth -
RFC destination error while importing a client request
Dear Experts,
We are trying to import a Client Export from our Prd system to Development System and we are unable to import the request as it pops up a RFC destination error.
We have checked the RFC in the Dev QAS and PRD related to TMSADM and all of them are working fine
FYI, We are able to release the transports from the development system and it can be moved till qas and prd . So the TMS Configuration is also good.
The data file and co file in the backend of development is the same size as that of the Prd system.
I am really stuck . Kindly suggest a solution . Please find the screenshots while importing
Regards,
Suratharajan .SHi Suratha,
Goto STMS->system overview and select the Communication tab.
Maintained the Instance number of the ASD system.
Once you maintained the instance number , you will able to see it in the RFC ASD.DOMAIN_ASD.
Also distribute the configuration after entering the instance number.
With Regards
Ashutosh Chaturvedi -
Mass Maintenance will recognize any customer record in workflow process
Hi gurus,
Please help me on the Workflow process, how to handle below workflow scenario, is there any logic be hand this.
please see in BOLD workflow issue.
1.2 As-Is Business Process
Currently Data Maintenance teams use standard SAP transaction XD07 to change Customer Account Groups. The standard transaction XD07 allows only one Customer Account Group to be changed at a time. The process is to be manually repeated for every customer. After the Account Group is changes in the request client (X07(10)), an RFC call is made to the BOR client (X07(20)) and then to the transaction client (X08(10)) to change the Customer Account Group as the SAP ALE process does not support Account Group Changesu2026
1.3 To-Be Business Process
From time to time, bulk customer data updates will be needed. This can be the result of business situations that cause multiple updates to be performed for given customer fields such as Customer Account Group field. A new program must be developed to let the user mass update the Customer Account Group field (KNA1-KTOKD). The Program should be accessed on demand using a new T.Code (YMDM_ACCTGRP_CHG).
Business users will submit a spreadsheet in the appropriate upload format to CDM along with written approval from the Food Service data owner to execute the upload in P07. CDM will execute the upload, record all documentation for the audit change log and notify the submitter when complete
1.4 To-Be Business Process Flow Diagram
1.5 Enhancement Functionality
The following are the requirements:
u2022 This tool will enable a user to perform bulk update to the customer account group field.
u2022 The utility should let the user upload a u201CTab delimitedu201D file to mass update the Account Group field.
u2022 The Load File will have 3 columns, Customer Number (KNA1-KUNNR), Current Account Group (KNA1-KTOKD) and New Account Group (KNA1-KTOKD).
u2022 The Program must utilize the process behind the standard SAP transaction XD07 to change customer Account Groups in X07(10).
u2022 The standard customer ALE (DEBMAS) process does not support Customer Account Group changes, so the mass change program must use the RFC functionality to change he Account Groups in the BOR (X07(20)) and Transaction system (X08(10)).
u2022 Workflows for all updates performed using this T.Code are automatically approved. No manual approval steps will be needed after data load.
u2022 Mass Maintenance will recognize any customer record that has an open workflow. If a customer record is already in the request queue, it is u201Coff limitsu201D for any bulk update. That update request to that particular customer record must be rejected.
u2022 Provide the option to run the process in validation mode and update mode.
u2022 Report all hard and soft legacy field errors on a validation report. All u201Chardu201D legacy field validations should be passed before allowing update mode to run.
u2022 The upload process will produce an error log for all records not loaded into the system.see newer message. Problem appears to be related to gmail
-
Mass maintenance and BDC Recodring of custom fields added in PO header.
Hello Experts,
I have created a custom fields in PO header and used Structure for BADI implementation to update the header with values enterd in custom table.
My requirement is for some selected PO i want to fix the value of one of my custom field at header level.
I have tried both the options Mass maintenance and BDC recording but the issue i'm facing is when i go for mass maintenance it is giving me the ERROR and it seems that we can only do the mass maintenance for sap-standard fields only.
When i go for BDC recording i'm facing the issue that when i do SHDB and start recording for ME22N my custom field is coming grayed out and i'm not able to input the desired value in custom field and complete my recording.
Let me know your valuable inputs .
Thanks,
NaveenHello,
Instead of BDC i'm doing it through the BAPI "BAPI_PO_CHANGE" by populating the structure extensionin but here i'm facing the error as below:-
W ME 887 Error transferring ExtensionIn data for enhancement CI_EKKODB
E BAPI 003 Instance 4500001544 of object type PurchaseOrder could not be changed
below is my code:-
ls_extensionin-structure = 'BAPI_TE_MEPOHEADER'.
ls_extensionin-valuepart1+0(10) = wa_po-ebeln.
ls_extensionin-valuepart1+14(3) = no.
append ls_extensionin to lt_extensionin.
clear:ls_bapi_te_bg,ls_extensionin.
ls_extensionin-structure = 'BAPI_TE_MEPOHEADERX'.
ls_extensionin-valuepart1+0(10) = wa_po-ebeln.
ls_extensionin-valuepart1+10(1) = 'X'.
append ls_extensionin to lt_extensionin.
clear:ls_bapi_te_bg,ls_extensionin.
call function 'BAPI_PO_CHANGE'
exporting
purchaseorder = wa_po-ebeln
tables
return = it_bapireturn
extensionin = lt_extensionin
if it_bapireturn[] is initial.
call function 'BAPI_TRANSACTION_COMMIT'
exporting
wait = ' '
importing
return = it_bapireturn.
endif.
refresh lt_extensionin[].
endloop.
Please let me know if there is any way to achieve this.
Thanks,
naveen -
RFC Destination Between R/3 and XI Not Reestablishing
I have an RFC destination set up in R/3 so that calls can be made to our XI system. Everything works fine until our central SLD goes down for maintenance,etc. When the SLD is down, the RFC connection is lost. I assume this is by design. The problem is that once the SLD comes back up, I would expect the RFC Destination connection to automatically re-establish itself. It does not. I have to go into IB:Config and change/save/reactivate a channel using the RFC destination so that it gets reregistered.
Is there a setting that will make the RFC Destination connectivity re-establish itself automatically?
ThanksWhen you say "go add some spaces" are you referring to putting spaces in the description field just so you can change/activate? I assume you did, just checking.
Thanks Naveen.
Everyone else out there: Do you all have to manually do this every time the SLD goes down?
Maybe you are looking for
-
Problem :ALV:Deletion Flags not showing in output
hi all ! I have a alv program which displays customer data.there are three deletion flags columns in the output. First deletion flag will be: KNA1-LOEVM Second deletion flag will be: KNB1-LOEVM Third deletion flag will be: KNVV-LOEVM earlier all thre
-
REJECT statment to break GET event is Obsolete in ECC 6.0 - Alternative?
Hi Developers, REJECT statment is used to break from GET event (say GET PERNR event in Logical Database) used to process for an Employee. This REJECT statement is Obsolete . Is there any alternative for this ? If so, please reply at the earliest as i
-
Why won't CS6 load brush shape dynamics from brush presets?
I have a bunch of saved brush presets that I use on multiple computers and photoshop versions. In CS6 suddenly my brush presets won't load correctly when I pick a brush. When I pick a brush I'll get all the correct brush settings EXCEPT for the Shape
-
Help with Firefox seperating spacing in words!?
Firefox has spaced letters and words extremely far apart, and to the point where I cannot read it anymore. I have tried uninstalling and reinstalling but this did not work. Take a look at what I mean: Google's "I'm feeling lucky" has a bunch of space
-
Invalid Phone Number Message why ?
I am from UK & trying to call the USA Mobile Number but each time i get an error saying Invalid phone number ? I have called this number many times before & had no problem then suddenly it has stopped working.