Badi/exit/Workflow called during  execution of the BSP "SRMSUS_SELFREG"

Hi all,
We are running on SRM 5.0.(SP06) Strategic sourcing scenario.We are using enterprise Portal as the front end.My query is that at the end of Supplier  registration process,when the Supplier admin creates the USER ID's for the Suppliers(through BSP SRMSUS_SELFREG),is there any way by which we can create the enterprise Portal users for those suppliers at the same time(Automation) ?My BASIS person told me that the automation is possible when the EP system is connected only to 1 backend but in our landscape we are having several systems connected to EP.
Other alternative would be to send a mail to the EP administrator stating that the Vendors User ID's have been created in SRM and the EP ID's need to be created.
For this ,i didnt get any BADi/exit which gets triggered during this USER ID creation process wherein i can write my logic for sending the mail to the EP admin.
There are some Std workflows (e.g. WS10000209)for USER creation but these dont seem to be useful in this scenario.
So the only method left is to modify the Std BSP which  we dont want.Has anybody worked on this kind of scenario?
Any suggestions are welcome and will be rewarded as well.
BR,
Disha.

Hi
I am still searching.. but no BADI/Exit is called in this case..
<u>Meanwhile, i found few SAP OSS notes, which you can go through -></u>
Note 1031896 Delimiting of Supplier Reg URL due to Special characters
Note  1031070 Supplier cannot be registered
Note  996030 Need to relogin to srmsus_selfreg service when using aliases
Note 1032573 FormofAddr field mandatory in userselfreg.htm page
Note 1003820 Supplier cannot be registered
Note 889451 Not Possible to register in Supplier self-registration
Note  807511 Error message after self registration of supplier admin user
Note 784883 Irrelevant warning message stops self registration
Do let me know.
Regards
- Atul

Similar Messages

  • A Windows Workflow Foundation workflow failed during execution

    Needed to know if there was some way to identify what the workflow was that is causing this error? I see this: "Workflow Identifier: 0cb64340-3a44-009e-67af-70963215b839" just not sure what SMLet I can use to see what this corresponds too.
    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          1/2/2013 1:56:56 PM
    Event ID:      33880
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      scsm
    Description:
    A Windows Workflow Foundation workflow failed during execution.
    Workflow Type: Microsoft.EnterpriseManagement.WorkflowFoundation.ConfigurationWorkflow
    Workflow Identifier: 0cb64340-3a44-009e-67af-70963215b839
    Exception Type: Microsoft.EnterpriseManagement.Common.ObjectNotFoundException
    Exception Message: An object of class ManagementPackRelationship with ID 6ec982d4-207f-da19-3bc9-e6d2ff7b067e was not found.
    Exception Stack:    at Microsoft.EnterpriseManagement.Configuration.TypeSpaceCache.Get[T](Guid id)
       at Microsoft.EnterpriseManagement.EntityTypeManagement.GetRelationshipClass(Guid id)
       at Microsoft.EnterpriseManagement.WorkflowFoundation.ConfigurationWorkflow.prepareNotificationActivity_ExecuteCode(Object sender, EventArgs e)
       at System.Workflow.ComponentModel.Activity.RaiseEvent(DependencyProperty dependencyEvent, Object sender, EventArgs e)
       at System.Workflow.Activities.CodeActivity.Execute(ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
       at System.Workflow.Runtime.Scheduler.Run()
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Modules" />
        <EventID Qualifiers="49152">33880</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-01-02T19:56:56.000000000Z" />
        <EventRecordID>1098867</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>scsm</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Microsoft.EnterpriseManagement.WorkflowFoundation.ConfigurationWorkflow</Data>
        <Data>0cb64340-3a44-009e-67af-70963215b839</Data>
        <Data>Microsoft.EnterpriseManagement.Common.ObjectNotFoundException</Data>
        <Data>An object of class ManagementPackRelationship with ID 6ec982d4-207f-da19-3bc9-e6d2ff7b067e was not found.</Data>
        <Data>   at Microsoft.EnterpriseManagement.Configuration.TypeSpaceCache.Get[T](Guid id)
       at Microsoft.EnterpriseManagement.EntityTypeManagement.GetRelationshipClass(Guid id)
       at Microsoft.EnterpriseManagement.WorkflowFoundation.ConfigurationWorkflow.prepareNotificationActivity_ExecuteCode(Object sender, EventArgs e)
       at System.Workflow.ComponentModel.Activity.RaiseEvent(DependencyProperty dependencyEvent, Object sender, EventArgs e)
       at System.Workflow.Activities.CodeActivity.Execute(ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
       at System.Workflow.Runtime.Scheduler.Run()</Data>
      </EventData>
    </Event>
    Help

    Everytime I run it I get nothing.
    Tried using the workflow identifier: 0cb64340-3a44-009e-67af-70963215b839 and tried this number as well: 6ec982d4-207f-da19-3bc9-e6d2ff7b067e
    Both just take me to the prompt with no info.
    EVENT ID 33880 Health Service Modules is the event title.
    Help

  • How can I show and hide an image or a decoration on the front panel during execution of the vi?

    Hello,
    I've made a user interface with a little grafic description.
    That description should change depending on user actions, e.g. if the user switches a button, some lines should disappear and some other lines should appear.
    I thought some decorations could be shown and hidden via something like a property node, but that is not possible. Images can also not be hidden during execution of the program.
    Is there any posibility to change a grafic user interface?
    Johannes
    LV 7.1
    Greetings Johannes
    Using LabVIEW 7.1 and 2009 recently
    Attachments:
    LV_Grafic.JPG ‏21 KB

    Thanks to Tim for drawing what I suggested as option while I had some real work to do.
    There is a trick of overcoming the index problem that was presented/devloped in the forum in the last month's: 
    You can place the decoration inside a cluster, so you can use the lable of the cluster to adress the decoration you want. The data type of the cluster doesn't mather for this, so you will hide the control/indicator. And you colour the cluster transparent (hint: right click with the coloring tool and use space to toggle). 
    Felix 
    www.aescusoft.de
    My latest community nugget on producer/consumer design
    My current blog: A journey through uml

  • How to view the SQL statement generated during execution of the BW Query?

    Dear Experts,
    I am trying to retrieve data in a SAP BW Query from a Non-SAP system.
    I think if I am able to see the complete SQL statement that was generated when I executed the BW Query, I may be able to use it to retrieve the data.
    Do you know how and where I can see the SQL statement of a BW Query's SQL statement?
    I tried RSRT options to execute the Query but still could not find the SQL statement.
    Thanks in advance.
    Regards,
    Shunhui.

    hi
    goto rsrt
    give your query name
    select execute + debug option
    in the debug option under data manager check the check box "display SQL/BIA query
    selcet continue
    you can see the sql statement
    thanq

  • How can we call windows application inside the bsp ...

    hi,
    i just want to call the exe file or execute or open outlook express inside a page...
    or.. openeing a notepad..
    thanks
    jaideep

    Check this thread..
    Call a Systemcommand from BSP
    how to call DLL in BSP
    <i>*Reward each useful answer</i>
    Raja T

  • Fpga: Re-Initialize Block Memory during Execution

    Hello,
    I am working on a project in labview fpga 2010, using the Spartan 3e board. At the present, I am using a large chunk of block memory in a VI and initialize it using an initialization VI that reads values from a spreadsheet and places them in the memory. It works for the first time, however I want to be able to re-initialize the memory during execution of the VI (i.e. I overwrite all the values in the table, then after a certain time I wish to reset them back to their initial values). Is there any way of accomplishing this on the FPGA without using double the memory and simply writing the changed values in a different location while leaving the originals unharmed? Thanks for your help

    I think the approach I would take to solve this would be as follows:
    Protect access to the block RAM with helper VIs that provide some level of locking (see http://zone.ni.com/devzone/cda/epd/p/id/6014 for some ideas)
    Lock the block RAM when you're about to change it, and the go ahead and push the new values to the FPGA, pull the old values to remember them on the host, or both
    Unlock when you've completed updating the RAM contents.
    Note that, depending on how large this block RAM is, this approach could be painfully slow (since the Spartan 3E boards don't support DMA, you'll have to create your own mechanism for pushing the data to the device)

  • .seq name available during execution of edit substep?

    Hello,
    I have a case where I'd like the sequence file name to be availalbe during execution of the edit substep.  Normally, during running of an actual sequence, this would be available under the runstate tree, but this does not appear to get populated by merely running an edit substep.  Is there a property in existence that is contains the sequence file name during edit substep execution?

    Depending on what property you have available, you have a few properties that you could use.
    If you pass a step object into your edit substep, you can use Step.Sequence.SequenceFile.Path
    If you pass a sequence context into your edit substep, you can use SequenceContext.SequenceFile.Path
    Be careful using this property, as it is common to add steps that belong to a sequence file that has not been saved.  In this case, the Path property will return an empty string.
    Hope this helps!
    Allen P.
    NI

  • Moving indicators during execution

    I would like to be able to move indicators during execution of the program by clicking on them and moving them to their new position. Is it possible to do this? Thanks.

    This link should give something to start with. It shows how to determine if a control has been clicked and moes them around.
    http://sine.ni.com/apps/we/niepd_web_display.displ​ay_epd4?p_guid=B567D7146B98028AE034080020E74861&p_​node=DZ52041&p_source=external
    I seem to remeber an old example that demo'd click and dragging but I can not find it. It may have been a LTR example.
    I hope this helps,
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • How to reconnect to a database if connection is lost during execution

    How to reconnect to a database if connection is lost during execution of the program.
    Please help me.
    thanks in advance.

    First close the old connection with "connection.close();" Catch all exceptions in case close() fails. Then open a new connection just like you opened the original one.

  • Unhandled exception occurred during the execution of the workflow instance

    I had a workflow and library working with no issues, but had to move the library and export the workflow to another subsite (though on the same web site/collection).  I followed these how-tos:
    http://msdn.microsoft.com/en-us/library/office/jj819316%28v=office.15%29.aspx
    http://technet.microsoft.com/en-us/library/ee428301%28v=office.15%29.aspx
    Anyway, I've stripped all actions from the workflow and only have an Assign Task, but get this below:
    An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ArgumentException: ContentTypeId at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
    instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
    To troubleshoot, I removed all library columns, removed then re-added the Custom Content type the New Document uses, and still the same error - with the workflow going into Suspended mode.
    I also tried the removal of the file from /Relationships%20List/allitems.aspx and de-activating then re-activating the SharePoint Publishing feature, also that didn't work.
    I've gone into ULS, but unable to find anything definitive, so not sure what to try next?
    Thank you,
    Chad

    Hi Chad,
    Glad to hear the issue is resolved. Content types could be used for multiple lists in SharePoint site at the same time.
    However, I'm not quite sure why you said the resolution is for a "bug". I read the article per your link:
    http://www.andrewconnell.com/blog/SP2013-Workflow-Custom-Task-Outcomes
    The article is showing how to create custom outcomes buttons in task forms. As I understand, the issue you encountered is that workflow migrated from the other site shows the suspended status.
    Please be more specific on the issue if assistance is needed. If this is the second question, I’d recommend you open another thread in the relevant forum and provide specific information about the issue. In order to avoid confusion and keep track of troubleshooting
    steps, we usually troubleshoot one issue per thread in order to find a resolution efficiently.
    Thanks for the understanding.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • How to schedule a workflow for recurring executions: The solution

    Scheduling a workflow for recurring execution has been long awaited in WFA, perhaps from 2.0 time. The following document shows how to get it done. I've also explained the logic behind it. It’s very simple to use, meets every requirement which one can have from a scheduler and of course highly flexible. Let's go!! The Real stuff. What is this? Is this actually a scheduler? No. This is actually a command in your workflow, but a special 'magical' command. This 'magical' command logic is built using the answers for the following questions: Can a workflow be scheduled for a delayed execution in a future time? Yes, but only one execution instance. If you want the next execution, execute the workflow again providing the same set of inputs and the execution date/time.During workflow execution, can a command inside a workflow get to know what is the  name of the workflow? YesDuring workflow execution, can the command know what is the job execution id? YesIs there any programmatic interface available to know what are the user input provided or a particular job execution? YesCan a command inside a workflow trigger another workflow? Yes.Can a command inside the same workflow trigger itself? Absolutely yes. I've ticked all boxes needed to build such a solution. The solution is to make the workflow a smart workflow, so smart that it can schedule itself for the next execution. It no longer needs any other task scheduler to tigger it. WFA provides a large set of REST APIs for other 3rd part SW integration. But I  also can make  good use of these APIs to make smart workflows. I have always believed that WFA should not only be seen as a framework for automating Storage boxes or server, but just about any task( inside a computer of course) which is done manually. WFA is an awesome product indeed.  So this is a command called "Workflow Scheduler" which  you can put in your workflow as another command. Prerequisites: You need PowerShell 3.0 on your WFA server. I certainly could have done it for PoSH2.0 as well, but life for web interfaces  using PowerShell is so much easier with Posh3.0. Posh3.0 is a big jump from 2.0. WFA is fully supported to work on Posh3.0. Its available by default in Win2012, Win2008 can be upgraded, Win2003 users can't use it. Add credentials of a WFA Admin/Architect in you WFA itself with Name/IP: localhost Match: ExactType: OtherName/IP: localhostUsername: <WFA Admin/Architect Username>Password: <User Password>   3.  Minimum WFA version 2.2. This is only needed for Importing the dar. I've provided the command code in text too. The command code is the real deal. How to use it? If you have a workflow which you want for recurring executions, just add this command "Workflow Scheduler" in it. The command takes parameters for the workflow execution intervals. For example minsInterval for executing this workflow every x minutes, or daysInterval for executing the workflow etc.Now just like a normal workflow execution execute this workflow deciding what is the trigger time. Example: Suppose you want the execution every day at 10:00 PM.So provide daysInterval = 1 And execute the workflow for a delayed execution at 10:00 PM. You can pick the day to start as you wish. The workflow will execute at 10:00 PM and when this execution reaches our magical command "workflow scheduler", this command will trigger the same workflow  with same set of inputs for the next execution at 10:00 PM tomorrow. And so on an so forth. I’ve attached a very simple example workflow here to help you understand. An Example of a workflow scheduled for recurring execution Daily at 11:30 PM starting 10-March-2015     How to stop/suspend this recurring execution? Easy. You just abort the next scheduled job execution in Execution=> Execution Status. The cycle will stop. How to resume it? Easy again. Just resume the same aborted job. The cycle restarts. Can I change the schedule execution time? Yes. After aborting the current execution, you can resume the same workflow at a new time. Execution interval can't be modified as you can't change the command parameters. But the recurring execution now can occur at a new time. Where or which position to place this “workflow scheduler” command in your workflow? At the beginning ? At the end? Or somewhere in the middle. This completely depends on your choice. See some below cases. You don't want the next job execution scheduling to happen if any of the commands in my current workflow execution fails: Put command “workflow scheduler” in the end. It will trigger the schedule of the next job execution only when all real original commands of your workflow have passed. else not.     You want continuous job executions irrespective of the workflow command failures: Put it in the beginning. It will trigger the schedule for next execution before any of the actual command begin executing.     You want an approval before the next execution job is scheduled: Add an approval point before the comamnd.           So it’s all left to you.      Can an operator decide the execution schedule? Yes, but which workflows will be available to him/her for this recurring execution will have to be decided by the designer. This is a good thing to have as it serves for access control in a way. The Architect/Admin can now restrict which workflow can be put for recurring executions. Operators can’t execute just any workflow available to him for automatic recurring execution. And the workflow designer can also choose which scheduling parameter is to be made a variable for the operator. For example the designer want the operator to schedule a given workflow only for weeks Interval and not months or days i.e. he/she can only chose to schedule for weekly, biweekly etc. executions and  nothing else. For this the designer can define a User-Input variable only for weeksInterval parameter. It’s Done. You want workflow execution to be scheduled either for daily or once in 2 days but not any other. You can restrict this. Or he/she wants to give full freedom to the operator make his/her own decision about scheduling, he defined user-input variable for all scheduling parameters. The workflow designer wants weekly schedule but the day should not be a weekday: You can even do this. Is this flexible enough for my requirements? I’ve attached the very command code. You can modify the command as per your requirements. Suppose you want daily execution of a certain workflow at 10:00 PM but skip a day of execution if the day is a Monday. Modify the code check for the day and add another day if it’s a Monday. Its posh code and highly readable. So you can see how this can be used in a  variety of ways. This is the beauty of a programmatic solution. Its highly flexible, it allows users to design solution based on their requirements. Flexibility is the heart & soul of WFA. Thats why I like it. I have a workflow but I don't want to modify it by adding a new command in it. Can I still use this solution? Yes but with WFA 3.0 on wards. WFA3.0 allows to create modular workflows. Create a parent workflow with you actual workflow as a child workflow in it. Add our “workflow scheduler” command too. So now you don't need to touch your existing workflow. I've attached a workflow example here.   Have fun!! sinhaa  

    Providing a new version 1.1.0 of the command "WFA Schedular" Changes made: Added conditional String Representation based on the Scheduling parameter provided. Provided check for the right number of parameters passed into the command.Added a new parameter "Expiry Date" to automatically stop the recurring execution upon expiry.Check for Posh3.0 version in code.Have Fun!! sinhaa Below example for:Schedule a workflow for recurring execution every alternate day i.e. once in 2 days at 10:30 PM starting 06-Jul-2015 (Today's date is 02-Jul-2015) . The recurring workflow execution  should expire on 31-Dec-2015 and stop.  

  • BADI/EXIT/Enhancement spot in during creation of PO to edit Vendor partner

    Hello,
    I am looking for BADI/EXIT/Enh. spot to edit the vendor partner during creation of a PO.
    Due to some business requirement we maintained multiple vendor partner( for same role like goods supplier) in the vendor master and for such cases during creation of PO it throws a pop-up to choose one of the partners. However, in some cases, I have to select a particular vendor partner based on some other field value, and suppress the pop-up.  So to choose the right vendor partner I need a suitable location where I can put my program logic.
    Looking forward to your replies...
    Thanks in advance.
    Best Regards,
    Amarjit Singh

    By now I am unable to test this BADI to see which data is retrieved and the moment that this happens. But the popup that you mentioned is a Z routine ?? If yes couldn't  you put your logic there?
    Regards,
    Felipe

  • Badi / Exit / Enhancement for replacing INSMK during PO creation

    Hi Gurus,
    we want to default the INSMK field (stock type) during Purchase Order creation..
    Can someone help me findind the right BAdI / exit / enhancement for it?
    Thanks in advance,
    Regards,
    Alessio

    Hi Alessio,
    You may check these first:
    Re: Negative postings to MVER table
    Re: select stock type
    Thanks,
    Gordon

  • An error has ocurred during the execution of the Extract_Rom

    I have this problem
    Trouble Ticket Report----
    Upgrade to SAP NetWeaver'04s
    SID................: J2E
    Hostname...........: sapepd
    Install directory..: d:/usr/sap/J2E
    Upgrade directory..: D:\usr\sap\jupgrade
    Database...........: Microsoft SQL Server
    Operating System...: NT
    JDK version........: 1.4.2_11 Sun Microsystems Inc.
    SAPJup version.....: 1.1.101
    Source release.....: 630
    Target release.....: 700
    Current usages.....: DI;EP;AS
    ABAP stack present.: false
    The execution of PREPARE/EXTRACT/EXTRACT_ROMS ended in error.
    0 of 1 extractions have been successful. 1 extractions have not been
    successful. See previous messages.
    Could not extract AKK from mount point D:\DVD\51031778 Kernel7
    \KU_WINDOWS_I386. See previous messages.
    Could not execute file system operation with name Extract and
    parameters archive:SAPEXE.SAR,
    target_dir:D:\usr\sap\jupgrade\data\kernel.
    The SAPCAR process has ended with an error exit code 6. See
    D:\usr\sap\jupgrade\log\EXTRACT_SAPEXE.SAR_ROM_08.OUT.
    More information can be found in the log file
    D:\usr\sap\jupgrade\log\EXTRACT_ROMS_ROM_08.LOG.
    Use the information provided to trouble-shoot the problem. There might
    be an OSS note providing a solution to this problem. Search for OSS
    notes with the following search terms:
    com.sap.sdt.ucp.phases.PhaseTypeExtractRom
    com.sap.sdt.ucp.tools.dda.ManagedRomsException
    0 of 1 extractions have been successful. 1 extractions have not been
    successful. See previous messages.
    EXTRACT_ROMS
    PREPARE
    NetWeaver Upgrade
    SAPJup
    Java Upgrade
    END of Trouble Ticket Report----
    *******************BEGIN THE EXTRACT_ROMS_ROM_08.LOG********
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[D:\usr\sap\jupgrade\log\EXTRACT_ROMS_ROM_08.LOG]/>
    <!PATTERN[EXTRACT_ROMS_ROM_08.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC10C8070000000006E60010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#PREPARE/EXTRACT/EXTRACT_ROMS#
    #1.5#C000AC10C8070000000006E70010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom#
    #1.5#C000AC10C8070000000006E80010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java###  Parameter =#2#dialog#ExtractRom#
    #1.5#C000AC10C8070000000006E90010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java###  Parameter =#2#romFile#RequiredRoms.xml#
    #1.5#C000AC10C8070000000006EA0010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:696)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:696)#Java###Checking phase parameters .#2#dialog#romFile#
    #1.5#C000AC10C8070000000006EB0010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:702)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:702)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#2#
    #1.5#C000AC10C8070000000006F80010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    LABEL.ASC#
    #1.5#C000AC10C8070000000006F90010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031807JAva Components
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000006FA0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    LABEL.ASC#
    #1.5#C000AC10C8070000000006FB0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000006FC0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_SRM
    LABEL.ASC#
    #1.5#C000AC10C8070000000006FD0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_SCM
    LABEL.ASC#
    #1.5#C000AC10C8070000000006FE0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_ERP
    LABEL.ASC#
    #1.5#C000AC10C8070000000006FF0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_CRM
    LABEL.ASC#
    #1.5#C000AC10C8070000000007000010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    LABEL.ASC#
    #1.5#C000AC10C8070000000007010010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031778 Kernel7
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000007020010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_LINUX_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007030010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_LINUX_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007040010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_I386
    LABEL.ASC#
    #1.5#C000AC10C8070000000007050010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_I386_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007060010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_IA64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007070010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_IA64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007080010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007090010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000070A0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_LINUX_X86_64
    LABEL.ASC#
    #1.5#C000AC10C80700000000070B0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_LINUX_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000070C0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386
    LABEL.ASC#
    #1.5#C000AC10C80700000000070D0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000070E0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_IA64
    LABEL.ASC#
    #1.5#C000AC10C80700000000070F0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_IA64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007100010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007110010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007120010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:95)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:95)#Java###Validatable parameter has been validated by validator .#2#DVDMountPointTable#DVDMountPointTable#
    #1.5#C000AC10C8070000000007130010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    LABEL.ASC#
    #1.5#C000AC10C8070000000007140010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031807JAva Components
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000007150010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    LABEL.ASC#
    #1.5#C000AC10C8070000000007160010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    LABELIDX.ASC#
    #1.5#C000AC10C8070000000007170010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_SRM
    LABEL.ASC#
    #1.5#C000AC10C8070000000007180010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_SCM
    LABEL.ASC#
    #1.5#C000AC10C8070000000007190010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_ERP
    LABEL.ASC#
    #1.5#C000AC10C80700000000071A0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031807JAva Components
    J2EE_OSINDEP
    UT_CRM
    LABEL.ASC#
    #1.5#C000AC10C80700000000071B0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    LABEL.ASC#
    #1.5#C000AC10C80700000000071C0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
    DVD
    51031778 Kernel7
    LABELIDX.ASC#
    #1.5#C000AC10C80700000000071D0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_LINUX_X86_64
    LABEL.ASC#
    #1.5#C000AC10C80700000000071E0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_LINUX_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000071F0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_I386
    LABEL.ASC#
    #1.5#C000AC10C8070000000007200010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_I386_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007210010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_IA64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007220010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_IA64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007230010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007240010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KN_WINDOWS_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007250010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_LINUX_X86_64
    LABEL.ASC#
    #1.5#C000AC10C8070000000007260010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_LINUX_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007270010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386
    LABEL.ASC#
    #1.5#C000AC10C8070000000007280010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386_AUPG
    LABEL.ASC#
    #1.5#C000AC10C8070000000007290010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_IA64
    LABEL.ASC#
    #1.5#C000AC10C80700000000072A0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_IA64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000072B0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_X86_64
    LABEL.ASC#
    #1.5#C000AC10C80700000000072C0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_X86_64_AUPG
    LABEL.ASC#
    #1.5#C000AC10C80700000000072D0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:139)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:139)#Java###Process ID , name has been started.#2#36#SAPCAR#
    #1.5#C000AC10C80700000000072E0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:141)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:141)#Java###Command line: #2#  #D:
    usr
    sap
    jupgrade
    exe
    SAPCAR -xvf D:/DVD/51031778 Kernel7/KU_WINDOWS_I386/DBINDEP/SAPEXE.SAR -R D:
    usr
    sap
    jupgrade
    data
    kernel#
    #1.5#C000AC10C80700000000072F0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:142)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:142)#Java###Standard out: #2#  #D:
    usr
    sap
    jupgrade
    log
    EXTRACT_SAPEXE.SAR_ROM_08.OUT#
    #1.5#C000AC10C8070000000007300010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#36#
    #1.5#C000AC10C8070000000007310010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#36#SAPCAR#
    #1.5#C000AC10C8070000000007320010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#36#SAPCAR#6#
    #1.5#C000AC10C8070000000007330010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#Java###The SAPCAR process has ended with an error exit code 6. See D:
    usr
    sap
    jupgrade
    log
    EXTRACT_SAPEXE.SAR_ROM_08.OUT.##
    #1.5#C000AC10C8070000000007340010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#Java###Could not execute file system operation with name Extract and parameters archive:SAPEXE.SAR, target_dir:D:
    usr
    sap
    jupgrade
    data
    kernel.##
    #1.5#C000AC10C8070000000007350010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#Java###Could not extract AKK from mount point D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386. See previous messages.##
    #1.5#C000AC10C8070000000007360010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC10C8070000000007370010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#Java###The SAPCAR process has ended with an error exit code 6. See D:
    usr
    sap
    jupgrade
    log
    EXTRACT_SAPEXE.SAR_ROM_08.OUT.##
    #1.5#C000AC10C8070000000007380010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#Java###Could not execute file system operation with name Extract and parameters archive:SAPEXE.SAR, target_dir:D:
    usr
    sap
    jupgrade
    data
    kernel.##
    #1.5#C000AC10C8070000000007390010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#Java###Could not extract AKK from mount point D:
    DVD
    51031778 Kernel7
    KU_WINDOWS_I386. See previous messages.##
    #1.5#C000AC10C80700000000073A0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:339)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:339)#Java###0 of 1 extractions have been successful. 1 extractions have not been successful. See previous messages.##
    #1.5#C000AC10C80700000000073B0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#PREPARE/EXTRACT/EXTRACT_ROMS#
    #1.5#C000AC10C80700000000073C0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/13 10:11:04#
    #1.5#C000AC10C80700000000073D0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/13 10:11:54#
    #1.5#C000AC10C80700000000073E0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:00:50.092#
    #1.5#C000AC10C80700000000073F0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
    /////////////////////////////////7END THE FILE////////////////////////777
    I read the notes and I donu00B4t find the problem
    Best Regards,
    Luis Moreno

    .

  • MIRO: Need a BADI/EXIT to clear the Payment Block 'R' :

    Hi Experts,
    I am looking for a BADI/EXIT to clear the Payment Block that is put by the standard sap code through Perform zahlungssperre_setzen in include LMRMPF1R.
    I have tried to use BADI MRM_PAYMENT_TERMS but this badi gets called before the above PERFORM zahlungssperre_setzen and hence any change made by the BADI gets overwritten by the SAP code again.
    Any inputs in this will be helpful.
    <offer removed by moderator>
    Regards,
    Edited by: Thomas Zloch on Jun 30, 2011 10:34 AM

    Hi
    See SAP Note 1559443 - Changing baseline dates for payment terms for Spain as a sample for this BADI. Read the documentation for the BADI in SE18.
    Try with this coding.
    First, load the interface of all e_*
    *--- fill all export-parameter ----------------------------------------*
      e_zfbdt = i_rbkpv-zfbdt.
      e_zbd1t = i_rbkpv-zbd1t.
      e_zbd1p = i_rbkpv-zbd1p.
      e_zbd2t = i_rbkpv-zbd2t.
      e_zbd2p = i_rbkpv-zbd2p.
      e_zbd3t = i_rbkpv-zbd3t.
      e_zlspr = i_rbkpv-zlspr.
    After, for instance
      if i_rbkpv-zlspr = 'Z'.   "or other
        clear e_zlspr.
      endif.
    And you would see that it works.
    I hope this helps you
    Regards
    Eduardo
    Edited by: E_Hinojosa on Jun 30, 2011 1:11 PM

Maybe you are looking for