BPS retraction RFC destination conversion

Hello everybody,
I m surprised not having met a discussion about RFC destination conversion between systems for BPS retraction?
What is the common recommendation for BPS retraction to have your customizing adapted and to retract to your QUAL R/3 from your QUAL BPS system without having to replicate your customizing with hard coded RFC destination to allow every BPS system to retract to any R/3 system !! Why this does not read the RFC conversion table from BW, probably too easy ?
If you have feed back on this point I would really appreciate , many thanks .
Laurent Allais

Hello Laurent,
I agree, it would be nice if the system would convert the RFC destinations. The functionality is just not there. You can use a single RFC destination for all systems and just have a different server that it is pointing to in SM59.
Or you just make a change in BPS0 after the transport.  It's quite common for plan administrators to have access to BPS0.
Regards
Marc
SAP NetWeaver RIG

Similar Messages

  • BPS retraction of Quantity in CO OM not retracting at all !

    Hi everybody, I post after many and many trials.
    I am retracting Primary Costs ( we have planned on CostElements for CO-OM Internal Orders) and I followed the blogs etc. Everything is fine for the Amount and it retracts ok by Posting Period but the quantities are not retracting at all.
    I also fixed the Unit as H as suggested because the quantity is in Hours and the R3 system expect that I retract hours for the CostElement related to Cost of Personnell.
    I don't move out from this position since long and I should deliver the project in 10 days .
    Any help is really really welcome.
    I used CCA retractor. This is the Parameter Group
    Retr. R/3 comp.          7
    Controllo retrattore          4
    Registrazione Delta          0
    Strutt. mitt.          UPB_SND_COPS
    Destin.          SVI100CDV
    Sess. test attiva          0
    VersioneR/3                                                           
    Att. registrazione          0
    Controlling area          01
    Voce di costo          02
    Tipo voce di costo          03
    Edited by: Walter Cista on Oct 26, 2008 10:04 PM

    Hi Marc,
    first of all my personal compliments because very often I follow your posts .
    Your answer let me "smell" the right way . Before to post I already debugged the retraction but at first look, if you don't feel that also somebody else found mistakes you can debug for hours and all looks fine. So this time I debugged with more attention and I found something strange in the Unit of Measures. In R3 the Cost Element expect H as Hours but in the RFC was going the quantity without the Unit of Measure. As I remember also in the blog about retraction the author said to take care about UOM. So I checked better Retraction about UOM and I found a OSS note . Anyway if this thread can be of help, I put here the list of OSS notes to be checked.
    The system where I work is always updated but I remember that sometimes especially in some cases where you miss some PIns or for many other reasons, (not good upgrades for example) the system in some part can remain not updated even if there are the proper HP.
    If I can help anybody with similar problems if JUST SEARCHING for  LUPREF02 in OSS NOTES you will find many !!!!
    1. 0.310 FIN-SEM-BPS-PLA 810478 SEM-BPS: Retraction of prices 19.01.2005
    2. 0.310 FIN-SEM-BPS-PLA 769889 SEM-BPS: Retraction Statistical Key Figures: distribution 08.09.2004
    3. 0.310 FIN-SEM-BPS-PLA 758350 SEM-BPS: Retraction prim. costs w/ cost element category 42 20.11.2006
    4. 0.310 FIN-SEM-BPS-PLA 1167790 SEM-BPS: Overhead cost retraction for individual periods 09.05.2008
    5. 0.310 FIN-SEM-BPS-PLA 884002 SEM-BPS: Data retraction of cost element categories 28.09.2005
    6. 0.310 FIN-SEM-BPS-PLA 909715 SEM-BPS: Retraction Cost Center 04.04.2006
    7. 0.310 FIN-SEM-BPS-PLA 922925 SEM-BPS: Retraction: Activities w/ cost element category 43 10.02.2006
    8. 0.310 FIN-SEM-BPS-PLA 889634 SEM-BPS: Primary costs: Retraction with quantities 16.07.2007
    9. 0.310 FIN-SEM-BPS-PLA 769337 SEM-BPS: Cost center retraction: distribution of activities 11.05.2006
    10. 0.310 FIN-SEM-BPS-PLA 822937 SEM-BPS: Retraction CCA: Statistical key figure with activit 15.03.2005
    11. 0.300 FIN-SEM-BPS-PLA 683947 SEM-BPS: Retraction activity types: price indicator = space 25.11.2003
    12. 0.300 FIN-SEM-BPS-PLA 900145 SEM-BPS: Primary costs: Data retraction with quantities 31B 21.11.2005
    13. 0.300 FIN-SEM-BPS-PLA 676133 SEM-BPS: Retraktion Gemeinkosten mit Transaktionswährung 04.11.2003
    14. 0.300 FIN-SEM-BPS-PLA 984644 SEM-BPS: Data retraction: Cost element category not checked 04.10.2006
    15. 0.300 FIN-SEM-BPS-PLA 894896 SEM-BPS: Overhead retraction with unit of measure 16.07.2007
    16. 0.300 FIN-SEM-BPS-PLA 810129 SEM-BPS: primary costs retraction with transaction currency 19.01.2005
    17. 0.300 FIN-SEM-BPS-PLA 553999 SEM BPS overhead costs retraction: Performance 13.09.2002
    18. 0.300 FIN-SEM-BPS-PLA 632619 SEM-BPS: Cost center retraction: Cost element categories 24.06.2003
    19. 0.300 FIN-SEM-BPS-PLA 513859 SEM-BPS: Cost center retraction for activities/prices 19.04.2002
    20. 0.300 FIN-SEM-BPS-PLA 818278 SEM-BPS: Retraction of overhead costs with trans crcy 352
    21. 0.290 FIN-SEM-BPS-PLA 821476 SEM-BPS: Cost center data retraction w/ Public Sector 352 / 22.02.2005
    22. 0.290 FIN-SEM-BPS-PLA 928893 Overhead cost planning: Retraction with sender process 24.03.2006
    23. 0.290 FIN-SEM-BPS-PLA 542059 SEM-BPS Overhead cost retraction: Setting period interval 01.08.2002
    24. 0.290 FIN-SEM-BPS-PLA 777794 SEM-BPS: Retraction prices with equivalence number 09.06.2006
    25. 0.290 FIN-SEM-BPS 520746 SEM-BPS: Over heads data retraction with object currency < > 16.05.2002
    26. 0.290 FIN-SEM-BPS-PLA 957281 SEM-BPS: Overhead cost retraction: Capacities 20.06.2006
    27. 0.290 FIN-SEM-BPS-PLA 801572 SEM BPS: Retraction of overhead costs with price unit 14.12.2004
    28. 0.290 FIN-SEM-BPS-PLA 862202 SEM-BPS: Cost center data retraction: Variable price 3.5 14.07.2005
    29. 0.290 FIN-SEM-BPS-PLA 823498 SEM-BPS: Cost center retraction: Variable price 15.03.2005
    30. 0.290 FIN-SEM-BPS-PLA 859435 SEM-BPS: Cost center retraction: Fixed and variable values
    31. 0.290 FIN-SEM-BPS-PLA 821472 SEM-BPS: Cost center retraction with Public Sector 352 / 3 22.02.2005
    32. 0.290 FIN-SEM-BPS-PLA 782320 SEM-BPS: Cost center data retraction with public sector 29.09.2006
    33. 0.290 FIN-SEM-BPS-PLA 821475 EM-BPS: Cost center data retraction w/ Public Sector 352/ 2
    Kind regards
    If anybody can help with material, pdf or something on SEM-BPS BCS and CPM I can be contacted trough www.sembps.com (the site is still under development)

  • Create a RFC destination with default pass word

    hi folk,
    I've a Z-program which creates a RFC destionation (SM59) with a default password. The RFC destination has been created successfully with all the necessary fields, but the pass word is not aticve.
    I'm using this fucntion module to scramble the pass word.
      slen = STRLEN( p_p_prfcpw ).
      SET EXTENDED CHECK OFF.
        CALL FUNCTION 'HTTP_SCRAMBLE'
          EXPORTING
            SOURCE            = p_p_prfcpw
            sourcelen         = slen
            key               = key
         IMPORTING
           DESTINATION       = p_pw
    I've got this message from SM59.
    Error in conversion of user password for destination A3
    Message no. SR131
    Diagnosis
    The upgrade to SAP Release 7.0 starts an XPRA program that converts passwords to secure storage. In certain cases, you may need to skip this procedure (for example, due to database locks during the upgrade). This can cause the passwords to become invalid.
    Procedure
    Enter the user password again.
    Any clues what is going wrong or how to solve this situation?
    Best regards
    Linhng

    hi Roberto,
    Everything is working except the pass word is not "converted" when I create the RFC destination in my z-program.
    So my question is still how do I create a RFC destination with the "correct" pass word.
    I've tried the function module  HTTP_SCRAMBLE to convert the pw and also without the FM.
    Best regards
    LinhNg

  • Prob with RFC destination - 4.5B 2 XI ABAP

    Hi,
    I created an RFC destination type 3(R/3 connection) in 4.5B, to address Integration Server.
    It gives the following error.
    <b>Connection error  : Conversation 09163404 not found / CPI-C error CM_PARAMETER_ERROR</b>
    Can any one guide me on this.
    -Naveen.

    Hi,
    Please check on 'Authorisation to Read Metadata'at the end
    http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
    Regards
    Vijaya

  • An RFC destination could not be specified for the logical system

    Hello Experts,
    I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
    An RFC destination could not be specified for the logical system
    SB3CLNT011
    Message No. B1550
    Diagnosis
    An RFC destination should be specified for the logical system SB3CLNT011.
    This could not be done in this case. SB3CLNT011 is not your local logical system
    and this system is not included in the relevant Customizing tables.
    Procedure
    Check:
    RFC
    destination
    Port
    definitions
    oubound partner profile of
    message type SYNCH for this logical system
    Regards,
    Khushboo

    Hi Oritra and Suraj,
    I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
    Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
    System SB3CLNT011 as a partner type already exists
    System SB3CLNT012 as a partner type already exists
    Port A000000018 with RFC destination SB3CLNT011 already exists
    Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
    Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
    Outbound parameters for message type SYNCH SYNCHRON already exist
    Am I missing something in WE20?
    Regards,
    Khushboo

  • Logical system and rfc destination

    hello all,
    what is the difference between logical system and RFC destination?
    thanks for ur help in advance.
    regards,
    vikas

    Hi,
    In any ALE scenario u need one sender and one receiver system.
    Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
    Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
    In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
    Regards

  • Logical system and rfc destination related Query?

    Hi Dudes
    Do we need to define logical system and RFC destination if they are in different clients in same server
    Regards
    Raj Kumar

    Hi
    Both are client independent setting, so even if you define in one client, it would be available in other clients also.
    Regards,
    Sanjeev

  • RFC Destination Connection Pool requirement

    Hi Experts,
    I have a custom webdynpro java application to display number of work items pertaining to that particular user in a backend.
    There are users who dont use this functionality as well. But the requirement is to place this application in home screen.
    I have used both metadata and modeldata with hard coded user since we did not want error messages to appear for users who do not have backend access.
    Application & Access Details
    Application Location : Home Screen
    Concurrent Users     : 600 concurrent users maximum possible value
    Connection Usage    : Close connection immediately using disconnectIfAlive() method.
    Now I need to configure JCO Pool Size , Max Connections, Wait Time for the RFC destination.
    I have read a lot of post and documents but could not acheive clarity of thought on this.
    Kindly let me know what values I should give in these fields for optimal performance and no connection issue for users.
    Regards,
    Porselvan

    Hi Muthavudaiyan,
    Hope you are doing good.
    Basically from the JCo perspective, there are only 5 parameters that are involved here:
    jco.destination.pool_capacity:
    Maximum number of connections that are held open in the pool for reuse (default: 1)
    jco.destination.peak_limit:
    Maximum number of connections that can be obtained from a pool at peak usage times
    jco.destination.max_get_client_time:
    Maximum time to wait for a free connection if the peak limit is reached before exception is thrown
    jco.destination.expiration_time:
    Timeout period after which pooled idle connections can be closed (default: 600000ms = 10mins)
    jco.destination.expiration_check_period:
    Regular time interval for checking if pooled connections have expired and will be closed
    The values are determined by the application in question. The ideal values have to told to you by the application developer; there are no two ways about this.
    Thank you and have a nice day :).
    Kind Regards,
    Hemanth

  • Service desk RFC destination in the Satellite system

    HI All,
          can any body tell me the RFC destination that is to be maintianed in the satellite system so that the message reaches the solution manager service desk.
    I am creating messages they are being send to the service desk successfully but are not visible when I go into the service desk of the solution.
    But they are visible through the transaction code CRM_DNO_MONITOR .Can any body help the RFC destination to be maintaned in the BCOS_CUST table so that the message reaches the Service Desk.]
    Currently I am using the RFC destination to the service desk client in the solution manager ie SIDCLNT200
    Thanks in advance
    Regards
    Amit

    Hi Amit,
    I think your expectation is not correct. I understood, you can create a message in a satellite system and you can see the ticket in SolMan service desk. Then everything is configured correct. What you are now looking for is to see the ticket in a solution when the sat. system is part of the solution. This is not working. If you create out of a solution a service desk ticket, these ticket get a special attribute that they belong to this solution, all other tickets can not be selected by a solution.
    Sorry but I am quite sure that it is working like this.
    There is only one option, that you define special variants so you can see only tickets from special systems, but these variants can not be assigned to a solution.
    Regards,
    uDo

  • How to create a RFC destination for extracting data to HANA

    Hello All,
    Could someone help me in providing a document or note on how to create a RFC destination for extracting data from SAP data source to HANA using SAP LT replication server ?
    I am able to create a data base connection while transforming data from non SAP data source,but wasnt able to transform data which is from SAP abap tables .

    Hi Venkatesh,
    In SM59 t.code we create RFC destinations.
    Go thru the video link for creating RFC destinations step by step
    How to setup a trusted RFC connection between SAP systems: a step-by-step guide - YouTube

  • Unable to change RFC destination in IT Performance reporting wizard

    Hi Experts,
    I am setting up IT Performance Reporting in my Solman EHP1 system. In the first page of the PErformance reporting wizard, it asked me for RFC destination from BI to Solman(1st field) and Solman to BI (2nd field). I initially entered an existing RFC destination that we are already using in a separate application that has a user with very-limited authorization. Now, I am trying to change the RFC destination by running the same "Configure IT Performance Reporting" wizard but both fields are already GREYED out.
    I tried deleting the RFC destination previously defined in an attempt to reenable the fields but only the 2nd field was enabled. When I try to continue the setup, it results into a Shortdump because it is still looking for the initially defined RFC dest which is defined in the 1st field that cannot be edited.
    SAP has not yet provided us with a solution.Your help is greatly appreciated.
    Thank you very much.

    You canprovide the RFC destination in DOE administration portal. Goto Configurations link and search for "BACKEND DESTINATION" parameter in "BACKEND CONFIGURATION" link. Here you can provide RFC destination at SWCV level or at Data object level.
    After deleting RFC destination in SM59, it will never take you to backend system.

  • Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist

    Hi Experts,
    I have one standard ALV report in ABAP Webdynpro.
    When i try to print the ALV Report it gives Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist.
    Can you give solution for this one.
    Regards,
    Sri

    Hi Sri
    Please go through this..
    /people/bv.pillai/blog/2007/01/09/webdynpro-abap-alv-print-versionpdf
    also Have a look this note SAP NOTE 918236; you will need help from basis.
    Cheers,
    Kris.

  • How to find out, which RFC-Destinations are in use?

    Hi community
    We have a huge list of RFC-Destinations in our productive system and I want to delete unneeded entries.
    Is there a report or a log, which shows, which RFC-Destinations were used, and when?
    Thanks in advance.
    Regards, Michael

    HI
    can you see the default trace in tcode SMGW, Be careful about deleting any system rfc.
    Read the documentation about default RFC, internal RFC, LDAP_RFC, transport RFC.
    I don't know other way to do that you need
    Regards
    William Neira

  • No RFC Destination maintained

    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
    FBF0F341000000000000000000000000000000000000000000000000000000000

    Hi 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 .S

    Hi 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

Maybe you are looking for

  • DVI out issues

    I have a Macbook Pro 10.6.4 2008 Model with details are below on graphics card and display options. I am trying two hookups to televisions which may or may not be possible. Can anyone tell me if my DVI output on the macbook pro is capable of deliveri

  • Probelm in  addition of line item in ME21N

    Hi, I am working on a requirement where after providing the data for line item 1 of a PO (ME21N),  when the User presses enter, based on certain conditions a new line item should get added to the PO. Using the BADI ME_PROCESS_PO_CUST and Method Proce

  • Error - An error occurred while attempting to establish an Applications Fil

    ERROR: An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_WIN2000. There may be a network configuration problem, or the TNS listener on node FNDFS_WIN2000 may not be running. Please contact your

  • Selecting from LIKP, LIPS & VBUK

    Will FOR ALL ENTRIES make the below SELECT faster?   SELECT kvbeln  sposnr  kerdat klfart k~cmfre AS erdat_d02            khandle ktsegfl k~sdabw            slfimg  svrkme  svgbel svgpos s~komkz            ucmgst  svolum  svoleh ktrspg kernam  ktddat

  • EAR / WAR Packaging

    Dear Expert, Do you know whether there is any guildline for packing EAR/WAR according to the J2EE standard? For example, whether several projects should be packed into the same EAR/WAR in order to reduce the overhead of starting up the applications (