We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-basis] Revolting SCC7: Forcing post processing steps through different releases (620 to 700)

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by Snowy (Certified Netweaver '04/Oracle Basis consultant)
on Oct 5 at 1:52 PM
Mark this reply as helpfulMark as helpful
Hi,

Post processing programs rely on table contents and structure,. when your imported data is not exactly the same format, SCC7 cannot handle the post processing adequately.

So, this is why you need to be in the same release.

---------------Original Message---------------
From: Palmintier
Sent: Tuesday, October 05, 2010 8:11 AM
Subject: Revolting SCC7: Forcing post processing steps through different releases (620 to 700)

> Hello professionals,
>
> After importing the customizing transport the TCODE SCC7 refused to do the postprocessing job with the message: "Releases of export and import systems have to be identical. Program ended abnormally".
>
> However, I want it to be this way. The plan is to fix the upcoming problems later on.
>
> Do you think it is a good idea to export and import a client copy with another TCODE from one of our systems with the same release?
>
> Hopefully someone had this journey already.
>
> A further basic question and for my own clarification: Afaik customizing is client dependent so the TCODE SCC7 should be executed whereby the customizing tables' clients are addressed correctly. Right? (i.e. now source 030 should be replaced by 100)
>
> Thanks in advance.
>
> Kind regards
> Peter

__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Snowy
SAP Basis Helper

Posted helpful replies on 50 threads in a group to earn a Silver Achievement
In the Spotlight
Toolbox.com for iPhone: Ask Questions & Get Answers Anywhere. Use the New iPhone App
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language