Monday, December 26, 2011

Other ways of starting Process Chains

If you want or need to avoid tracking of starting process chains by transport system asking you to provide transport request number there are few possibilities available.

  1. You can trigger process chain via standard ABAP Function Module: RSPC_API_CHAIN_START. Using this FM you can start PC that is scheduled to be executed via meta chain (Start via Meta-Chain or API) and you do want to change it to direct scheduling.
  2. Starting your PC via custom ABAP report. This report would call FM mentioned in point no.1.
  3. Start PC via event. You can maintain custom event in TA SM64. The event that you created than specify into PC’s start variant.
  4. Exclude changes into PC’s start variants and PC’s processes from BW’s Transport Connection. You can customize this in RSA1->Transport Connection->Object Changeability

Full Process Chain’s API:

- Update on 05/07/2017 -
Similarly there can be a case that you need to run the PC just one time. When the PC is scheduled already and you may do not want to de-schedule it. There is an option in RSPC1 t-code in menu called Execution -> Execute synchronously. By using this function the PC will run in dialog mode. All processes within the PC are executed serially and the PC is kept scheduled.

Online documentation on this topic:

Processing of SAP Support messages

SMP messages are kind of communication channel between SAP support organization and SAP’s customer. The aim is to support customers within their problems with SAP applications. Customer reports problems via SMP under /message link. There are 4 priorities (see below) defined from which customers can choose according problem’s severity. After submitting support message you may wonder what is the duty time range within SAP should respond. Please notice that this time may differ per particular contract between SAP and customer. Also if customer is using e.g. max attention product -> times may differ. However times specified below can serve as general guideline.

So to make it short the initial respond times/update periods and response goals are follows:

 Priority     Severity     Initial Response     Update period      Response goal
 ------     ---------    ---------------    --------------     ---------------
     1         very high     60 minutes           4 hours               2 days
     2         high             4 hours               1 day                  4 days
     3         normal         8 hours               2 days                8 days
     4         low              16 hours             4 days                16 days

For details see following SAP notes:

Comments in ABAP code 3

Here one very short but good one. It is included in BW 7.3 in method WRITE_DTP in class CL_RSDD_CUBE_WRITER :-)

Other posts on similar topic:

What are SAP Pilot Notes?

We all know SAP Notes; we all use them on daily basis along our job needs to. We search for an advice, explanation or fix of problems within SAP software. I already introduced differences between HotNews; TopNotes here

Today let’s say something about Pilot Notes. Basically it is very first version of SAP Note created by SAP development support. Usually it is SAP organization called IMS (Installed Base Maintenance & Support). When they provide correction for problem you reported via SMP (Service Market Place, formerly OSS) the note has status as Pilot release. If required later after note is tested by customers; note will be included in standard Support Pack for particular SAP software release. 

See details about Pilot release in following note:

Few more posts about SAP Notes topic: