NCo 3.0 Logon

One of the new features implemented to combat the malevolent for RFC client attacks is the interface IDestinationConfiguration. This interface contains method IDestinationConfiguration.GetParameters(string destinationName) which allows .NET programmers to provide their own secure method for storing and retrieving logon information, be it encrypted database, encrypted file, or even LDAP.  There is also a corresponding interface and method to secure NCo 3.0 RFC servers.

Additionally, there is updated functionality to support single sign-on (SSO) and X.509 certificates.

Say Goodbye to Data Containers and Generated Code

In SAP Connector 2.0, working with RFCs required the generation of proxy code via the SAP .NET Connector design-time tool.  This tool would convert the IMPORTING, EXPORTING, CHANGING, and TABLES parameters from the RFC you were calling/serving to .NET representations of the same.  With NCo 3.0 there is no longer any kind of generated code.  Instead of one generated proxy method for each function module, there is one single RfcFunction class, whose Invoke() method dynamically executes every given ABAP function module. Additionally, all ABAP parameters will be represented by the class RfcStructure instead of a dedicated generated class for every structure; All tables will be represented by class RfcTable.  So, instead of hard-coding all of the data and variable bindings statically at design time, NCo 3.0 now handles everything dynamically at runtime.

NCo 3.0 uses SAP’s data dictionary to determine the function interface for the called RFCs.  While this data is cached locally for performance reasons, NCo 3.0 is robust enough to detect changes in RFC interface signatures so your code will still execute if you’ve added, deleted, or changed RFC parameters.  If there arises a situation where the dynamic lookup of RFC interface signature is not wanted, there is also an option to hard code the RFC parameter metadata.

The biggest benefit of NCo 3.0′s new dynamic function handling is that NCo 3.0 no longer has a design-time component.  This releases the Visual Studio version restriction that .NET 2.0 had.  Let me rephrase that, NCo 3.0 will work with any version of Visual Studio you like! The only requirement is that at runtime, a .NET Framework version is installed that is compatible with the NCo 3.0 libraries.

Anxiously Waiting

NCo 3.0 figures to be a much-needed update to a vital SAP integration technology.  I, for one, cannot wait for the new functionality to be generally released.  Once NCo 3.0 is released we’ll be posting blogs highlighting the new features.  We’ll also include helpful information regarding a .NET Connector 2.0 to NCo 3.0 upgrade.  In the meantime, if you have any leave any questions or comments you have regarding NCo 3.0 below.  You may also email me directly at cstasila@dataxstream.com if you’d like to set up a detailed conversation.

This would, in turn, generate a short dump:

My initial thought was that this was a TemSe issue, meaning it was a true BASIS issue.  Upon further examination, I came to the conclusion that it was actually a security/access issue.  The user did not have create rights for TemSe.  Find the Role path Basis: Administration -> TemSe: Actions on TemSe objects -> TemSe: Action ID for Authorization and make sure that the user has the value “CRE” (for create).

It is possible to add transport requests to the buffer, and even import them via the CLI (Command Line Interface).  Keep in mind, whenever working on an instance at the OS level, you should be logged in as [sid]adm.

To add transports to the buffer: tp addtobuffer [transport number] [SID] Client=[client number] pf=/usr/sap/trans/bin/TP_DOMAIN_[DOMAIN_SID].PFL

If I wanted to add transport number DV1K907046 to the buffer for Q01 client 400 and the transport domain controller was DV1 the string would look like this: tp addtobuffer DV1K907046 Q01 Client=400 pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL

To import transports via CLI: tp pf=/usr/sap/trans/bin/TP_DOMAIN_[DOMAIN_SID].PFL import [transport number] [SID] U128 client=400

Since I’ve added DV1K907046 to the buffer, I can now import it with this string: tp pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL import DV1K907046 Q01 U128 client=400

It is also possible to create shell or batch scripts from these commands to do multiple transports at one time. I’ve found that this is when CLI tp management is most effective. Using your favorite text editor, simply “stack” the commands ontop of each other: tp addtobuffer DV1K907046 Q01 Client=400 pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL tp addtobuffer DV1K907047 Q01 Client=400 pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL tp addtobuffer DV1K907048 Q01 Client=400 pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL .... Then save as either a .sh for Unix or .bat for Windows.

The batching approach works for both adding to the buffer and for actual import. It’s best to seperate each task (addtobuffer in one script, import in another).

Q2Q3Y6XJM37U

Office/Excel 2003:

Open Excel

Tools -> macro -> security

Security Level tab: make sure level is set to “medium”

Trusted Sources tab: Check the box beside “Trust access to visual basic project.”

Office 2007:

Click the Office button.  Click Excel Options.

Click on Trust Center -> Trust Center Settings

Check the box beside “Trust access to VBA project object model”

Close Excel and try to view your report again.  The workbook should no longer be blank and it should be populated with the correct data.

Sometimes, a special business or security requirement does not permit the “business as usual” scenario.  It is these situations which nudge me down the path which I have never explored.

Take, for example, a simple flat file interface outbound from SAP to an external system.  In the typical scenario, at the 50,000 foot level, it works like this:

In a scheduled batch job step, an SAP ABAP program extracts data and creates a flat file in a folder somewhere on the network that is commonly visible to both SAP and the external system.

The external system acquires the flat file, processes the data and then archives the file, just in case we need to play “where is my data” or “I sent it, why didn’t you get it”.

Here is the process diagram:

In this scenario, OS administrators on both sides of the interface have agreed to grant to the common folder all of the permissions needed so that each side of the interface can perform its tasks.

But what if that is not the case?  What if the external system administrator cannot permit a common SAP/external system mount; but will permit receiving the file via ftp?

Let’s redraw the process diagram:

In this scenario, SAP drops the output file into its own outbound network OS folder. The file is then moved to an inbound network folder on the external system via an ftp script.

The question now becomes, how do we execute the ftp script after the first step of the batch job which creates the outbound data file?

It turns out that SAP provides a facility to do just that.  Effectively, SAP will allow the ftp script to be entered as a step in a batch job.

We begin to assemble our batch job with SM36 as usual.

As shown here, the batch job is named Z_OUT_INTERFACE_2_EXTERNAL_SYST.

The first step of the batch job executes ABAP program Z_OUT_MATERIAL_EXTRACT with variant PRODUCTION_VAR.

This is the step which creates the outbound data file.

Once the file is created by the ABAP program in step 1, we would like an ftp script to execute, and copy the file to a folder on the remote system. SAP allows an external program (e.g. our ftp script) to be executed as a batch job step.  We are going to  make this step 2 in our job. (This is the section of batch job land which I had never before explored.) To set up an external program as an SAP batch job step, click the External Program button. The External program block is now open for input.

In the Name box, enter the complete path name of the location of the external program. In this case, our external program is an ftp script which takes two input parameters: 1) The complete pathname of the data file. In this example, the complete pathname is /data/dx1/ftpscript.ksh. 2) The path name and the name of the outbound data file. In this example, the path name of the outbound data file is /data/dx1/interfaces/materials/outbound, and the name of the outbound data file is materials.txt. Both of these parameters are entered in the Parameter box.

SAP also allows for the external program standard output or error output to be displayed in the SAP job log. These are turned on/off using control flags.

In this example, I have turned on the control flags which allow any standard output and error output from the external program to be displayed in the SAP job log.  I have also set the control flag which requires that the external program complete before the SAP job ends.  If this control flag is not set and there are no further job steps, the SAP job will complete without waiting for the external program.

Here is the entire SAP batch job with two job steps. The first step is the ABAP program which creates the outbound data file. The second step is the ftp script which will ftp the file to the external system. This is the result that we want.

And, for all of you SAP documentation fans, yes, this is documented in SAP.  This documentation describes the external command and external program facilities, as well as the authorizations needed to utilize them.

SAP Documentation about using External Commands and External Programs as batch job steps can be found at: http://help.sap.com/saphelp_nw70/helpdata/EN/c4/3a7f2c505211d189550000e829fbbd/content.htm

This blog is a recap of the liveblog of the keynote address of the SAP TechEd 09 conference.  To read in chronological order, start from the bottom and work your way up.

• Craig Stasila: 8:57 am on October 13, 2009

  If you missed anything, check back for the full blog posting at http://www.dataxstream.com/category/sap-consultants-blog/

• Craig Stasila: 8:55 am on October 13, 2009

  Well, that’s it. The keynote speeches are over. I hope you enjoyed following along with the DataXstream’s first foray into liveblogging. Make sure you check back tonight at 11pm EDT (8pm PDT) for our liveblog of the Demo Jam.

• Craig Stasila: 8:53 am on October 13, 2009

  Ray’s parting shot: Even life expectancy is growing exponentially.

• Craig Stasila: 8:52 am on October 13, 2009

  2029: An intimate merger $1,000 of computation = 1,000 times the human brain Reverse engineering of the brain complete Computers pass the Turing test!! Skynet goes online (OK, I made this one up)

• Craig Stasila: 8:48 am on October 13, 2009

  There are only about 800 million bytes in the entire genome and it can be compressed into about 50 million bytes. The brain is made up of about 25 million bytes of data.

• Craig Stasila: 8:45 am on October 13, 2009

  

  The brain is getting reverse-engineered.  Individual brain components (e.g. visual cortex, cerebellum, etc.) are getting reverse engineered by researchers.

• Craig Stasila: 8:44 am on October 13, 2009

  Ray is now on Artificial Intelligence (AI). AI is all around us, but we’re too accustomed to it to notice it.

• Craig Stasila: 8:42 am on October 13, 2009

  They already had this technology in the 80s. I saw Innerspace (http://www.imdb.com/title/tt0093260/usercomments)

• Craig Stasila: 8:41 am on October 13, 2009

  Someday you will have millions or billions of nano-engineered devices coursing through your body keeping you healthy.

• Craig Stasila: 8:40 am on October 13, 2009

  Miniaturization is another exponential trend. “What used to fit in a building now fits in my pocket. What fits in my pocket now will fit inside a cell in a few years”

• Craig Stasila: 8:39 am on October 13, 2009

  Ray is now going over how the exponential growth in technology power is also mirrored by exponential decrease in price. RAM, processing power, human genome decoding, wireless devices. All adhere to the exponential growth curve.

• Craig Stasila: 8:38 am on October 13, 2009

  

  Ray thinks we’re due for a new paradigm shift away from flat integrated circuits.  He’s been talking to Intel about their development of 3D processors.  I’ve not heard of this before, but it sounds very cool.

• Craig Stasila: 8:34 am on October 13, 2009

  

• Craig Stasila: 8:32 am on October 13, 2009

  Some critics say that exponential growth can’t go on forever. Ray counters that by saying that there can be periods of relatively slow advancements, but over time, progress will catch up.

• Craig Stasila: 8:29 am on October 13, 2009

  You may think that he only picked events that matched his theory. But, now he’s showing another graph comparing his viewpoints with 15 others. There is a very high correlation.

• Craig Stasila: 8:27 am on October 13, 2009

  

  From life to now, this chart shows how life and technological advancements have followed a constant, exponential growth.  Both axes are logarithmic.  Very cool, indeed.

• Craig Stasila: 8:24 am on October 13, 2009

  

  As big as a washing machine.  Stevie Wonder bought one.  In 2002, it was still a desktop device.  Now, it is a cell-phone based app.

• Craig Stasila: 8:21 am on October 13, 2009

  It took 10 years to bet the first billion phones in the market. Now 2/3 of the world’s population has them!

• Craig Stasila: 8:20 am on October 13, 2009

  “The tools of disruptive change are in everybody’s hands”

• Craig Stasila: 8:20 am on October 13, 2009

  Technology is a democratizing force. Back in the day, you had to be a recording studio or movie studio to create content. Now a couple of hundred dollars can be used to create great content.

  • Craig Stasila: 8:18 am on October 13, 2009

    Back in the 70s, Ray projected that the two-thousand user ARPAnet would grow into a million user internet in the 90s. Umm. Yeah. I saw that coming, too!

  • Craig Stasila: 8:17 am on October 13, 2009

    Exponential growth even applies to solar energy. Solar energy may be a fringe player now, but Ray sees it growing.

  • Craig Stasila: 8:16 am on October 13, 2009

    This exponential growth is unaffected by any financial or other external pressures.

  • Craig Stasila: 8:15 am on October 13, 2009

    There are many underlaying properties of technology (MIPS, # of bits, # of genomes typed). Regardless of the property, technology follows a smooth exponential growth.

  • Craig Stasila: 8:13 am on October 13, 2009

    Not many pictures right now. Ray is just standing in one place and talking.

  • Craig Stasila: 8:12 am on October 13, 2009

    Only 10 years ago, people barely used search engines.  Now we can’t live without them.

    I’m always amazed how true genius can point out the obvious and make it sound profound.

  • Craig Stasila: 8:10 am on October 13, 2009

    Using the human genome project as an example of exponential growth in technology.

  • Craig Stasila: 8:09 am on October 13, 2009

    And progress is getting faster…

  • Craig Stasila: 8:09 am on October 13, 2009

    Your phone in your pocket is a thousand times more powerful and million times cheaper than a computer from 40 years ago. “What fit in a building 40 years ago, fits in your pocket today”

  • Craig Stasila: 8:08 am on October 13, 2009

    Ray thinks genes are software written in COBOL.

  • Craig Stasila: 8:08 am on October 13, 2009

    Oh Ray! Retalling the story of how Viagra was developed and discovered. Got a few chuckles from the crowd.

  • Craig Stasila: 8:06 am on October 13, 2009

    Ladies & Gentlemen, Ray Kurzweil

  • Craig Stasila: 8:06 am on October 13, 2009

    Vishal is done. Last parting shot: “Timeless Software”

  • Craig Stasila: 8:05 am on October 13, 2009

    

    Vishal’s only slide.  All the rest were just pretty pictures.  Notice the public clouds in the lower right.  SAP is looking to be able to be run on public clouds in the future.  Currently there are development and test systems on public clouds.  Getting production systems on public clouds is coming.

  • Craig Stasila: 8:03 am on October 13, 2009

    

  • Craig Stasila: 8:03 am on October 13, 2009

    “Change is the fundamental dimension in which we all live”

  • Craig Stasila: 8:02 am on October 13, 2009

    Cestbon “listens” for business content on your computer and links to it. You can hop straight from Cestbon to the data in SAP.

  • Craig Stasila: 8:01 am on October 13, 2009

    The presenter is British and doesn’t like the frenchies. Demoing Cestbon–An Outlook integration example.

  • Craig Stasila: 7:59 am on October 13, 2009

    Example #4: Ambient, Real-Time Systems

  • Craig Stasila: 7:59 am on October 13, 2009

    Six blade servers = 1 Nehalem processor.

  • Craig Stasila: 7:58 am on October 13, 2009

    Vishal is talking about optimization across all layers. This relates to hardware manufacturers (memory, processors, blade servers). Modularity is making optimization happen.

  • Craig Stasila: 7:57 am on October 13, 2009

    All the demos were very cool. As a geek, I would love to check out the technology involved in each one.

  • Craig Stasila: 7:57 am on October 13, 2009

    Excel integration now being demoed. The 166 million records can’t be loaded to Excel (for memory reasons). The solution allows the end-user to drill down and get the data from SAP as needed.

  • Craig Stasila: 7:55 am on October 13, 2009

    Business Objects Explorer being demoed. Crunching through 166 million records. The example is trying to be green by reducing paper and electricity.

  • Craig Stasila: 7:55 am on October 13, 2009

    

  • Craig Stasila: 7:53 am on October 13, 2009

    A Dilbert Example! Wow, the pop-culture touchpoints never end!

  • Craig Stasila: 7:52 am on October 13, 2009

    Example #3: Coherent Visualization of Massive Information. Looking at Coherent Modularization.

  • Craig Stasila: 7:50 am on October 13, 2009

    Containers need not only modularity, but also locality of design.

  • Craig Stasila: 7:49 am on October 13, 2009

    Now talking about SOA and its growth. Using it as a basis of modularity and coherence.

  • Craig Stasila: 7:49 am on October 13, 2009

    

    Too many tools on the stage… (ahem)

  • Craig Stasila: 7:47 am on October 13, 2009

    

  • Craig Stasila: 7:46 am on October 13, 2009

    Live tracking of tools being checked in and out of the tool crib.

  • Craig Stasila: 7:45 am on October 13, 2009

    Aircraft mechanics were using SAP, but equipment check-in check-out took too long via SAP GUI.

  • Craig Stasila: 7:43 am on October 13, 2009

    Example #2: Extending Information into Physical Systems. SAP runs on aircraft carriers. I hope they bring one in…

  • Craig Stasila: 7:42 am on October 13, 2009

    

    Google Wave and SAP!  So happy together.

  • Craig Stasila: 7:42 am on October 13, 2009

    Cutting edge technology BCE edition: Rosetta stone. Using the analogy to show that we need to be able to work with others

  • Craig Stasila: 7:38 am on October 13, 2009

    They’re pulling out all the stops!!! Google Wave! Google Wave isn’t complying with the demo. “Thank god that’s Google software and not SAP!” Big crowd laughs.

  • Craig Stasila: 7:37 am on October 13, 2009

    The example is now showing our good-ole familiar SAP GUI showing the timesheet approval process for the contractor timesheet application

  • Craig Stasila: 7:36 am on October 13, 2009

    Containers need to be extended. Either to SAP applications or to other Web 2.0 applications.

  • Craig Stasila: 7:35 am on October 13, 2009

    Another ooh-ahh moment! iPhone timesheet app.

• Craig Stasila: 7:34 am on October 13, 2009

  

  Content separated from applicatons

• Craig Stasila: 7:34 am on October 13, 2009

  Oh Snap!!! Cloud computing!! The example is running through a container. The backend is on Amazon S3

• Craig Stasila: 7:32 am on October 13, 2009

  Example uses managers, contractors, and purchasing department.

• Craig Stasila: 7:32 am on October 13, 2009

  Examples of design thinking, and separation of intent and optimization.

• Craig Stasila: 7:31 am on October 13, 2009

  An example of intent being separated from optimization: A painter does not need a scaffolding to paint a building, the scaffolding optimizes the process.

• Craig Stasila: 7:29 am on October 13, 2009

  

• Craig Stasila: 7:29 am on October 13, 2009

  Next, the intent needs to be separated from the optimization.

• Craig Stasila: 7:28 am on October 13, 2009

  Techies need to start with “design thinking”. Start with end-user in mind. “Start from the screen and work backwords”

• Craig Stasila: 7:27 am on October 13, 2009

  

• Craig Stasila: 7:25 am on October 13, 2009

  Content is independent of containers in long-lived systems

• Craig Stasila: 7:24 am on October 13, 2009

  Looking back at the IT industry, a new, major language emerges about every ten years. While Java will be around for a long time, we’re due for a new major language. SAP thinks that Ruby is the future. Ruby reached 1 million developers faster than any other programming language in history.

• Craig Stasila: 7:22 am on October 13, 2009

  Vishal is teasing Ray Kurzweil’s speach on how the rate of change is increasing. Moore’s law gets a shout out.

• Craig Stasila: 7:22 am on October 13, 2009

  There are hundreds of SAP customers that have been using the software for over 30 years. None have left SAP. Vishal is highlighting the change that the companies underwent and how SAP changed with their customers.

• Craig Stasila: 7:20 am on October 13, 2009

  SAP has been around for 37 years. Have worked with over 85,000 customers, tens of thousands of partners, and tens of millions of users.

• Craig Stasila: 7:19 am on October 13, 2009

  Vishal isn’t going to be focusing on the technology. He’ll be focusing on… “change”. Do you sense a theme?

• Craig Stasila: 7:18 am on October 13, 2009

  Dr. Vishal Sikka, CTO SAP is now on the stage. He is the first of two keynote speakers.

• Craig Stasila: 7:18 am on October 13, 2009

  

  “Welcome to TechEd 2009. You are the star of the show”

• Craig Stasila: 7:16 am on October 13, 2009

  Zia is really pumping up “the community”. The SAP user community is almost 2 million strong now.

• Craig Stasila: 7:16 am on October 13, 2009

  “After the PowerPoints, it’s time for action” SAP wants the BPEs to make it happen! I already feel pumped. Let’s go out there an do this!!!! Oh wait, the Keynote hasn’t even started yet.

• Craig Stasila: 7:14 am on October 13, 2009

  

  • To enter a new market, business process have to change. SAP’s emphasis on Business Process Expert community will pay dividends.

  • Craig Stasila: 7:12 am on October 13, 2009

    Zia is giving an example using Dunder Mifflin as a “well-run company”. Perhaps he hasn’t seen The Office…

  • Craig Stasila: 7:11 am on October 13, 2009

    Zia is telling the conference attendees that we are the agents of change–A very person-centric focus.

  • Craig Stasila: 7:11 am on October 13, 2009

    

  • Craig Stasila: 7:10 am on October 13, 2009

    The world is changing. SAP is changing.

  • Craig Stasila: 7:09 am on October 13, 2009

    Change is constant. Michael Jackson gets a shout-out!

  • Craig Stasila: 7:09 am on October 13, 2009

    On the stage now: Zia Yusuf, Executive Vice President, Global Ecosystem & Partner Group, SAP

  • Craig Stasila: 7:08 am on October 13, 2009

    Inspirational Video: “Clarity is a necessity”.

    and

    SAP: “It’s time for a clear new world”

  • Craig Stasila: 7:06 am on October 13, 2009

    And away we go. Lights down. Check. Ominous Music. Check. Inspiring Opening Video. Check. Can you feel the excitement?

  • Craig Stasila: 7:05 am on October 13, 2009

    

    The crowd is filling in nicely.  Sorry guy-behind-me for accidentally flashing the camera in your face TWICE before I snapped one without the flash.

  • Craig Stasila: 7:03 am on October 13, 2009

    

    Uploaded from backup backup plan.  This is from my iPhone.  Doug, Adam, Tim say “hi”

  • Craig Stasila: 7:00 am on October 13, 2009

    Cell phones off, y’all!

  • Craig Stasila: 6:59 am on October 13, 2009

    

    Pictures will be slow, but here is a teaser

  • Craig Stasila: 6:57 am on October 13, 2009

    Five minutes to go. With me are Tim Cooper, Doug Foss, and our good friend Adam Blum from Grom & Associates

  • Craig Stasila: 6:55 am on October 13, 2009

    

    Here we go!

  • Craig Stasila: 6:49 am on October 13, 2009

    We had an awesome setup to capture pictures from the event, but it relied on the conference WiFi. We’re working on a backup solution now.

  • Craig Stasila: 6:48 am on October 13, 2009

    The conference public WiFi isn’t working. I have to be working on backup off of my Verizon Aircard, so posts may be a little slower.

  • Craig Stasila: 6:47 am on October 13, 2009

    First take from the keynote address. The welcoming music is horrible, but we’ll survive

  • Craig Stasila: 6:45 am on October 13, 2009

    Welcome to the DataXstream Liveblog of the SAP TechEd 09 Conference Keynote address

Head over to live.dataxstream.com on Tuesday, October 13, 2009 to get up to second updates from the show.  We will be getting our liveblog on starting at 8am PDT (that’s 11am for you right-coasters) for the general keynote session.  We’ll also be liveblogging from SAP TechEd 09 Demo Jam at 8pm PDT on Tuesday.  The Demo Jam promises to be a great time, so plan to join us online after you put the kiddies to bed!

This is our first foray into liveblogging.  Hopefully it will go off without too many technical glitches.  We hope you’ll enjoy following the events with us!

From time to time it becomes necessary to change the status of SAP IDOCs in SAP. The most common scenario is the requirement to mark SAP IDOCs for deletion. There is no good way to mass mark IDOCs for deletion via the standard IDOC processing transaction BD87. However there is a program that will let you change status.

RC1_IDOC_SET_STATUS

CAUTION: This program should be used with great care and consideration. Improper use of this program can result in data consistency issues. Make sure you know what you are deleting, why you are deleting it, and what is required to correctly update you system after deleting.

Example: Marking IDOCs for Deletion In Mass

It is pretty typical for support users to set the deletion flag on IDOCs that have been incorrectly created and have errored. When there are a small number of IDOCs this is possible via transaction BD87.

An inbound IDOC in error will have the status 51, when it is marked for deletion it has a status of 68.

A view of the IDOCs to be deleted in WE05.

To mass delete IDOCs run the following program via SE38: RC1_IDOC_SET_STATUS via the SAP Transaction: SE38

There are only a few parameters on the selection screen for this program. It is most important that you correctly restrict the IDOCs you select with this program. The program automatically defaults to marking inbound IDOCs in error for deletion.

To mass select IDOCs to be marked for deletion select:

There are many options for selecting and restricting the IDOCs to Mass process. Select by single value or range. Restrict by single value or range.

The allows you to upload a list of IDOCs from a text file.

The allows you to apply a list from your clipboard.

Execute the program

Check the status of the 3 IDOCs in WE05

Example: Changing IDOCs Status To Repost

It is also possible to use this program to reset an IDOC so that it can be reprocessed.

With the following selection we are going to reset the IDOCs with status 68 marked for deletion back to status 64 to try and reprocess them.

Execute the program

As you can see, program RC1_IDOC_SET_STATUS is very helpful, but please be careful when you use it!

Scenario:

Our SAP servers are running on HP-UX hosts with Oracle 10g databases. Recently, the client underwent SPS application to production servers. The process called for the stopping of scheduled jobs during update. The jobs were to be restarted as directed by team leads. When a request to restart job was executed, it was unable to be completed because the required job had “disappeared”. The job in this scenario was over 100 steps with different programs and variants being executed. Due to time constraints and the possibility of incorrect data entry, manually recreating the job in SM36 was not an option.

It is possible to extract a job definition directly out of the tables in which it is stored and then reinsert it into another instance (i.e. copy the job definition from your Q box and drop it back in Production). For demonstration purposes we will call our source server Q01 and our destination server P01. The job used in this example will be OUR_LOST_JOB.

NOTE: The steps used in this tip may utilize commands that access and modify data in ways not explicitly endorsed by SAP. Therefore, the use of this tip should be done at your own risk.

1. In Q01 verify that OUR_LOST_JOB is available by looking for it in SM37 or searching table TBTCP via SE16.
2. Log into the Q01 unix host as q01adm ( <sid>adm ).
3. Using your preferred text editor, create a file named ‘sm37exp.r3tr and enter the following statements adjusting entries to match your landscape:

   Export client=[source client] file=’SM37export’ select * from tbtco where JOBNAME=‘OUR_LOST_JOB’ select * from tbtci where JOBNAME=‘OUR_LOST_JOB’ select * from tbtcp where JOBNAME=‘OUR_LOST_JOB’ select * from tbtcs where JOBNAME=‘OUR_LOST_JOB’ select * from btcctl where JOBNAME=‘OUR_LOST_JOB’ select * from btcsev where JOBNAME=‘OUR_LOST_JOB’ select * from btcuev where JOBNAME=‘OUR_LOST_JOB’ select * from btcsed where JOBNAME=‘OUR_LOST_JOB’ select * from btcued where JOBNAME=‘OUR_LOST_JOB’ select * from btcevtjob where JOBNAME=‘OUR_LOST_JOB’ select * from btcdelay where JOBNAME=‘OUR_LOST_JOB’

4. As q01adm, execute the following command: R3trans –u 8 –w sm37exp.log sm37exp.r3tr This string creates the SM37export file which contains the actual job definitions, as well as sm37exp.log. Review the log to ensure a successful export (warnings are OK).
5. Copy the SM37export file to P01 p01adm home directory (/home/p01adm) and make sure to chmod 777 to grant full permissions.
6. Login to the P01 CI unix host as p01adm
7. Use your favored text editor to create the file ‘sm37imp.r3tr’ with the following contents: import client=[destination client] file=’SM37export’ buffersync=yes

8. Execute the following command in /home/p01adm: R3trans –u 8 –w sm37imp.log sm37imp.r3tr
9. Check the log to see if the import was successful
10. Log into P01 and search for OUR_LOST_JOB via SM37. It should be under status: Finished.
11. To recreate the job in “scheduled” status, execute menu “Job->copy”

The job has now been copied and is in status: “Scheduled”. From here you can either manually release the job or reschedule it for its proper frequency.