ECC 6 Dev  problem

HI,
I have 2 Dev Clients in ECC 6  one is gold and another one is unit test. I dont have any autharization for gold client.
I am doing total migration steps in unit test client only. Now i need to change delta mode from direct delta to queued delta and set up V3 job .Client has changed that step in gold server but that's not reflected in unit test client.
and i tried request copy in SCC1 also. its also not working.
can u give me any suggestions on this.

If they don't show in SAPMMC means that the services are not started... start the services open the MMC again and it all be there.
Having said that, this is well known, please search before posting and read the "Rules of Engagement"
Regards
Juan

Similar Messages

  • XI Dev. connected to ECC Dev and ECC Qas

    Hello Folks,
    I have a question -
    We have 2 XI systems: Development, and Production (no QAS)
    And 3 ECC systems: Dev, Qas and Prd.
    Now we have the XI Dev connected to the ECC Dev.
    I'd like to know if it's possible to also connect the XI Dev System to the ECC Qas system.
    I mean, to create the RFC dest. in both systems, a new Business System for ECC QAS; and all the necessary config.... and if it won't take problems when we have to transport the Interfaces from DEV to PRD.
    Thanx in advance.
      Juan

    Hi juan,
    just be carefull when you add you QUA config in ID and then when you will transport...
    1. in your ID, when will define the config with QUA, do NOT ADD the object to your Scenario.... if for the transport you choose the option "Transport all objects of my Scenario"... else you will have a problem in Prod because of the system QUA. Indeed with transport DEV become PROD but your ECC QUA cannot become ...
    2. when you will transport to your PI prod :
       - check my first point or use option "Transport by selecting each objects" and choose only object linked link to your DEV.
       - delete also the Condition option (if you have one) in the Receiver Determination if in th receivers list you have DEV and QUA.... because after the transport the ECC QUA become nothing.
    So yes we can. There is no technical issue.... if you do properly the things !!
    Regards.
    Mickael

  • ECC dev to new PI sandbox to be point in ABAP proxy configuration

    Hi All ,
    We are testing ABAP proxy configuration between ECC Dev and PI new system (sand box) .
    FYI : Currently ABAP proxy configuration running fine between ECC DEV and PI DEV system .
    Now we have to testing ABAP proxy configuration between ECC Dev and PI new system (sand box) .
    Pls advise what needs to be done.
    thanks

    Dear All,
    Any relation between SLD and Abap proxy configuration ?
    FYI:
    1,ECC SLD is running fine with PI DEV sysytem (PI7.1).
    2,in ECC SAPSLDAPI RFC destination program id is pointing to PI DEV system .
    3,In Ecc LCRSAPRFC RFC destination program id is pointing to PI DEV system .
    4, PI DEV system is PI7.1
    5, PI Sandbox is PI 7.4 SP06 (note : currently we are testing all the interface , PI scenario in new sand box - it is newly upgraded PI system . )
    6.In ECC SXMB_adm -> Role of Business System -> Application system
    Corresponding Integ. Server -> dest://RFCDESTINATION (H connection type RFC created in ECC SM59.
    Below is my question.
    1, Latest PI version required H og  G type connection ?
    2, SLD (sldapicust,lcrsaprfc,sldapicust,rz70)related information needs to point to PI new upgraded dsystem for ABAP proxy testing in new sand box?
    pls advise.

  • Error while posting GR from EWM in ECC. "Problem with receiver finding"

    Hi
    I have completed putaway of inbound delivery in EWM. This has triggered PPF to ECC for GR posting. This is stuck in ECC SMQ2 with error "Problem with receiver finding".
    I have checked ECC>EWM interface configuration. Handling unit management setup in ECC and EWM. Do not see any issues there. Also tested GR account postings with IM storage location for Po in ECC. This is also working fine...so no issue with account determination.
    Unable to figure out what is causing issue. Please help. Thank you.
    Best Regards
    phani sai MN

    Hi All
    Thanks for your responses. Issue was with distrubution model fiter parameters. for message type InboundDelivery.Deliverychange there was additional filter parameter for logical system. Removed values for logical system and only retained warehouse number.
    With this issue is resolved. GR is posted succesfully in ECC.
    Best Regards
    Phani sai MN

  • Compatability of ECC DEV&QAS on Win 2008/SQL 2008 with Prdn on Win 2003/Win

    We are planning our  upgrade of my SAP landscape (ECC 6.0 , Portal & BI) . Would it be feasible and do-able to migrate sandbox, dev, and qas to Windows 2008 & SQL 2008 , allow the support team to use the 2008 landscape.  That means that my Dev. environments would be on Wind 2008 & SQL 2008 while my production would still be Win 2003 & 2008.   I'm not feeling like this is workable for the transport domain? will I have issues with transports across to production?
    So the question is
    Is it possible to transport from Windows 2008 SQL 2008 landscape over to a production landscape that is on Windows 2003 SQL 2005?
    Any other issues I should be aware of ?
    BTW, we would have Portal and BI setup in the same way  DEV & QAS on the newer releases and Production on the Older release.
    NOTE: this would be for about 3 - 4 weeks
    Please advise
    Maria

    Thank you,
    So you're saying that if I had the DEV environment in Win 2008 SQL 2008 (being the transport domain) , and the production environment in win 2003 sql 2005, IF we had to transport across this type of landscape there should be NO issues. 
    Nothing else to think of as posing risk?
    Maria

  • Migration From SQL Server 2005 to Oracle DB through Oracle SQ Dev Problem

    Hi all,
    we are trying to do a full Migration from MS SQL Server 2005 to Oracle DB 9.2 i
    we are using Oracle SQL Developer V 1.5.3,
    the capturing of the DB and the conversion to the oracle model completed succefully
    however when we try to generate the scripts from the converted model
    the script generation hangs on a sequence and no further progress is made (the script generation pop up keeps still on a certain sequence displaying its name, and thats it )
    no error messages are displayed,
    how can we know the reason for this? or atleast find a log for whats happening...
    any suggestions?
    Thank you

    Hi,
    migrating a sequence shouldn't make a problem. I did a quick test. I created this table in SQL Server:
    create table test_seq (col1 int identity(1,1),col2 char(1))
    Then I captured the table, converted the table and generated the script. There was no problem.
    CREATE SEQUENCE succeeded.
    CREATE TABLE succeeded.
    Connected
    TRIGGER test_seq_col1_TRG Compiled.
    As you see, applying the script was also successful.
    I am using Oracle RDBMS 11g, I don't know whether this makes a difference. Do you have any 11g instance available to test it?
    Can you show me one of the sequences that are causing the hang? Is the CREATE SEQUENCE statement already in the generated script, or not? Your table is for sure more complex than my simple example.
    Regards,
    Wolfgang
    Edited by: wkobargs on Jan 13, 2009 3:01 AM

  • Elliptic cryptography (ECC), set problem

    Hi All,
    I have problem with my public key.
    Sets the point of the curve comprising the public key in the method setW.
    initialization methods of ECKey is OK: setFieldF2M, setA, setB, setG, setR, setK
    initialization methods of ECPrivateKey is OK: setS
    bul initialization methods of ECPublicKey is NOT OK: setW
    because I have CryptoException.getReason = ILLEGAL_VALUE 0x0001
    my code:
    package pacApplet;
    import javacard.framework.*;
    import org.globalplatform.*;
    import javacard.security.*;
    import javacardx.crypto.*;
    public class Applet extends javacard.framework.Applet {
        private static final short MAX_COMPONENT_SIZE = (short) 88;
        private static final byte TYPE_EC_F2M_PUB = (byte) 0x0009;
        private static final byte TYPE_EC_F2M = (short) 0x09;
        private static final byte INS_SET_KEYLENGTH = (byte) 0x01;
        private static final byte INS_SET_COEF_PRIV = (byte) 0x02;
        private static final byte INS_SET_COEF_PUB = (byte) 0x03;
        private static final byte INS_SET_W = (byte) 0x04;
        private static final byte OBJECT_DELETION = (byte) 0x0A;
        private static final byte DEFINE_KEY_INS = (short) 0x0B;
        private static final byte DO_KA_TEST = 0x0C;
        private static final byte DO_SIG_TEST = 0x0D;
        private SecureChannel secureChannel
        private short keyLength;
        private short code = 0;
        private KeyPair keyPairECC;
        private ECKey _ecKey;
        private static ECPrivateKey _ecPrivatKey;
        private static ECPublicKey _ecPublicKey;
        private Cipher _cipher;
        protected Applet(byte[] bArray, short bOffset, byte bLength) {
         try {
             _ecPrivatKey = (ECPrivateKey) KeyBuilder.buildKey(
                  KeyBuilder.TYPE_EC_F2M_PRIVATE,
                  KeyBuilder.LENGTH_EC_F2M_113, false);
             _ecPublicKey = (ECPublicKey) KeyBuilder.buildKey(
                  KeyBuilder.TYPE_EC_F2M_PUBLIC,
                  KeyBuilder.LENGTH_EC_F2M_113, false);
         } catch (CryptoException e) {
             ISOException.throwIt(e.getReason());
         } catch (ClassCastException e) {
             ISOException.throwIt((short) 0xE006);
         byte aidLen = bArray[bOffset];
         if (aidLen == (byte) 0) {
             register();
         } else {
             register(bArray, (short) (bOffset + 1), bArray[bOffset]);
         // register(bArray, (short) (bOffset + 1), bArray[bOffset]);
        public static void install(byte[] bArray, short bOffset, byte bLength) {
         // GP-compliant JavaCard applet registration
         new Applet(bArray, bOffset, bLength);
        public void process(APDU apdu) {
         apdu.setIncomingAndReceive();
         byte buf[] = apdu.getBuffer();
         if (selectingApplet()) {
             code = DecKeys.VERSION_INFO_MAJOR_MINOR;
             return;
         try {
             switch (buf[ISO7816.OFFSET_INS]) {
             case (byte) DEFINE_KEY_INS: // vyber kluca
              break;
             case (byte) INS_SET_COEF_PRIV:
              _ecPrivatKey.setFieldF2M(TYPE_EC_F2M);
              _ecPrivatKey.setA(DecKeys.valA_F2M, (short) 0,
                   (short) DecKeys.valA_F2M.length); // is OK
              _ecPrivatKey.setB(DecKeys.valB_F2M, (short) 0,
                   (short) DecKeys.valB_F2M.length); // is OK
              _ecPrivatKey.setG(DecKeys.valG_F2M, (short) 0,
                   (short) DecKeys.valG_F2M.length); // is OK
              _ecPrivatKey.setR(DecKeys.valR_F2M, (short) 0,
                   (short) DecKeys.valR_F2M.length); // is OK
              _ecPrivatKey.setS(DecKeys.VALS_SECRET_KEY, (short) 0,
                   (short) DecKeys.VALS_SECRET_KEY.length); // is OK
              _ecPrivatKey.setK(DecKeys.valK_cofactor);
              code = DecKeys.SW_DEFINE_KOEF_CURVES;
              break;
             case (byte) INS_SET_COEF_PUB:
              // public key
              _ecPublicKey.setFieldF2M(TYPE_EC_F2M);
              _ecPublicKey.setA(DecKeys.valA_F2M, (short) 0,
                   (short) DecKeys.valA_F2M.length); // is OK
              _ecPublicKey.setB(DecKeys.valB_F2M, (short) 0,
                   (short) DecKeys.valB_F2M.length); // is OK
              _ecPublicKey.setG(DecKeys.valG_F2M, (short) 0,
                   (short) DecKeys.valG_F2M.length); // is OK
              _ecPublicKey.setR(DecKeys.valR_F2M, (short) 0,
                   (short) DecKeys.valR_F2M.length); // is OK
    //=============problem======================
              _ecPublicKey.setW(DecKeys.VALW, (short) 0,
                   (short) DecKeys.VALW.length); // is NOT OK  - CryptoException
    //===========================================
              _ecPublicKey.setK(DecKeys.valK_cofactor);
              code = DecKeys.SW_DEFINE_KOEF_CURVES;
              break;
             case (byte) DO_KA_TEST:
              if (buf[ISO7816.OFFSET_CDATA] == (byte) 0x01) {
                  if (!_ecPrivatKey.isInitialized()) {   // IS TRUE
                   code = DecKeys.ER_KEY_NOT_INITIALIZET;
                  } else {
                   code = DecKeys.SW_DEFINE_KOEF_CURVES;
              } else if (buf[ISO7816.OFFSET_CDATA] == (byte) 0x02) {
                  if (!_ecPublicKey.isInitialized()) { // IS FALSE
                   code = DecKeys.ER_KEY_NOT_INITIALIZET;
                  } else {
                   code = DecKeys.SW_DEFINE_KOEF_CURVES;
              }else{
                  code = DecKeys.ER_KEY_NOT_INITIALIZET;
              break;
             default:
              // good practice: If you don't know the INStruction, say so:
              ISOException.throwIt(ISO7816.SW_INS_NOT_SUPPORTED);
         } catch (CryptoException ce) {
             code = ce.getReason();
             ISOException.throwIt(code);
         } catch (ClassCastException e) {
             code = DecKeys.ER_CRYPTO_EXCEPTION;
         } catch (NullPointerException ne) {
             code = DecKeys.ER_NULL_POINTER_EXCEPTION;
         Util.setShort(buf, (short) 0, code);
         apdu.setOutgoingAndSend((short) 0, (short) 2);
    }and
    cm>  send d00311110000
    => D0 03 11 11 00 00                                  ......
    (328748 usec)
    <= 00 01                                      // Set public is CryptoException  ILLEGAL_VALUE  0x0001;     ..
    Status: 0x0001
    cm>  send d00211110000
    => D0 02 11 11 00 00                                  ......
    (349749 usec)
    <= A0 04 90 00                            //Set private is OK            ....
    Status: No Error
    cm>  send d00C1111010100
    => D0 0C 11 11 01 01 00                               .......
    (103274 usec)
    <= A0 04 90 00                              //test _ecPrivatKey.isInitialized() is true          ....
    Status: No Error
    cm>  send d00C1111010200
    => D0 0C 11 11 01 02 00                               .......
    (117022 usec)
    <= E0 03 90 00                          //test _ecPublicKey.isInitialized() is false               ....
    Status: No Errorand next my value
        public static final byte[] VALS_SECRET_KEY = { (byte) 0x10, (byte) 0xE7,
             (byte) 0x23, (byte) 0xAB, (byte) 0x14, (byte) 0xD6, (byte) 0x96,
             (byte) 0xE6, (byte) 0x76, (byte) 0x87, (byte) 0x56, (byte) 0x15,
             (byte) 0x17, (byte) 0x56, (byte) 0xFE };
        //Value for setW
        public static final byte[] VALW = { (byte) 0x10, (byte) 0xE7, (byte) 0x23,
             (byte) 0xAB, (byte) 0x14, (byte) 0xD6, (byte) 0x96, (byte) 0xE6,
             (byte) 0x76, (byte) 0x87, (byte) 0x56, (byte) 0x15, (byte) 0x17,
             (byte) 0x56, (byte) 0xFE, (byte) 0xBF, (byte) 0x8F, (byte) 0xCB,
             (byte) 0x49, (byte) 0xA9 };
    public static final short ER_KEY_NOT_INITIALIZET = (short) 0xE003;
    public static final short SW_DEFINE_KOEF_CURVES = (short) 0xA004;Can you help me?
    How do I remove my problem?
    Could you tell me why I can not initialize function _ecPublicKey.setW(VALW, (short) 0, (short) DecKeys.VALW.length); and why I have CryptoException?
    Thank you.
    Edited by: johny3212 on Aug 12, 2009 11:02 PM

    Thank you for the help But I have a new problem with my Sign and Verify.
    _sign2.verify(......) = "false" when initiated keys my own parameters and I do not know why it is "false" . :).
    but ecPrivateKey, ecPublicKey.isInitialized() = "true";
    When initializes with default domain parameters "genKeyPair()" so my Sign and Verify is OK (true), problem is when I set my own values (setA,setB,setG, ....)
    package pacApplet;
    import javacard.framework.*;
    import org.globalplatform.*;
    import javacard.security.*;
    import javacardx.crypto.*;
    public class Applet extends javacard.framework.Applet {
        private byte[] scratch;
        private static byte[] valA_F2M; //next post
        private static byte[] valB_F2M;
        private static byte[] valG_F2M = { (byte) 0x04, (byte) 0x02, (byte) 0xFE,
             (byte) 0x13, (byte) 0xC0, (byte) 0x53, (byte) 0x7B, (byte) 0xBC,
             (byte) 0x11, (byte) 0xAC, (byte) 0xAA, (byte) 0x07, (byte) 0xD7,
             (byte) 0x93, (byte) 0xDE, (byte) 0x4E, (byte) 0x6D, (byte) 0x5E,
             (byte) 0x5C, (byte) 0x94, (byte) 0xEE, (byte) 0xE8, (byte) 0x02,
             (byte) 0x89, (byte) 0x07, (byte) 0x0F, (byte) 0xB0, (byte) 0x5D,
             (byte) 0x38, (byte) 0xFF, (byte) 0x58, (byte) 0x32, (byte) 0x1F,
             (byte) 0x2E, (byte) 0x80, (byte) 0x05, (byte) 0x36, (byte) 0xD5,
             (byte) 0x38, (byte) 0xCC, (byte) 0xDA, (byte) 0xA3, (byte) 0xD9 };
        private static byte[] valR_F2M = { (byte) 0x04, (byte) 0x00, (byte) 0x00,
             (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
             (byte) 0x00, (byte) 0x00, (byte) 0x02, (byte) 0x01, (byte) 0x08,
             (byte) 0xA2, (byte) 0xE0, (byte) 0xCC, (byte) 0x0D, (byte) 0x99,
             (byte) 0xF8, (byte) 0xA5, (byte) 0xEF };
        private final static byte[] valS_F2M = { (byte) 0x04, (byte) 0x0C,
             (byte) 0x66, (byte) 0xA6, (byte) 0x44, (byte) 0x59, (byte) 0x48,
             (byte) 0x4B, (byte) 0x85, (byte) 0x65, (byte) 0x7C, (byte) 0x5D,
             (byte) 0x64, (byte) 0x0A, (byte) 0x24, (byte) 0xED, (byte) 0x3C,
             (byte) 0x75, (byte) 0x49, (byte) 0x83, (byte) 0x5F };
        private final static byte[] valW_F2M = { (byte) 0x04, (byte) 0x0C,
             (byte) 0x66, (byte) 0xA6, (byte) 0x44, (byte) 0x59, (byte) 0x48,
             (byte) 0x4B, (byte) 0x85, (byte) 0x65, (byte) 0x7C, (byte) 0x5D,
             (byte) 0x64, (byte) 0x0A, (byte) 0x24, (byte) 0xED, (byte) 0x3C,
             (byte) 0x75, (byte) 0x49, (byte) 0x83, (byte) 0x5F, (byte) 0x6E,
             (byte) 0xFB, (byte) 0x5B, (byte) 0x71, (byte) 0x9E, (byte) 0xF7,
             (byte) 0x6A, (byte) 0x42, (byte) 0xF7, (byte) 0x88, (byte) 0x68,
             (byte) 0xFF, (byte) 0xA9, (byte) 0x91, (byte) 0x6D, (byte) 0x50,
             (byte) 0x85, (byte) 0x29, (byte) 0xB9, (byte) 0xE6, (byte) 0xA6,
             (byte) 0x55 };
        public static final short valK_cofactor = (short) 0x0002;
        private static final short MAX_COMPONENT_SIZE = (short) 88;
        private static final byte INS_SET_COEF_PRIV = (byte) 0x01;
        private static final byte INS_SET_COEF_PUB = (byte) 0x02;
        private static final byte INS_SET_W = (byte) 0x04;
        private static final byte INS_GET_ALGORITHM_INSTANCE = 0x0A;
        private static final byte INS_DEFINE_KEY_INS = (short) 0x0B;
        private static final byte INS_KEY_INITIALIZET_TEST = 0x0C;
        private static final byte INS_SIGN = 0x0D;
        private static final byte INS_VERIFI = 0x0E;
        private final static short e1 = 0x0007;
        private final static short e2 = 0x0006;
        private final static short e3 = 0x0003;
        private short code = 0;
        private KeyPair keyPairECC;
        private ECKey _ecKey;
        private static ECPrivateKey _ecPrivatKey;
        private static ECPublicKey _ecPublicKey;
        private Signature _sign1;
        private Signature _sign2;
        protected Applet(byte[] bArray, short bOffset, byte bLength) {
         try {
             scratch = JCSystem.makeTransientByteArray((short) 255,
                  JCSystem.CLEAR_ON_DESELECT);
             keyPairECC = new KeyPair(KeyPair.ALG_EC_F2M,
                  KeyBuilder.LENGTH_EC_F2M_163);
             keyPairECC.genKeyPair();
             _ecPrivatKey = (ECPrivateKey) keyPairECC.getPrivate();
             _ecPublicKey = (ECPublicKey) keyPairECC.getPublic();
             _sign1 = Signature.getInstance(Signature.ALG_ECDSA_SHA, false);
             _sign2 = Signature.getInstance(Signature.ALG_ECDSA_SHA, false);
             byte aidLen = bArray[bOffset];
             if (aidLen == (byte) 0) {
              register();
             } else {
              register(bArray, (short) (bOffset + 1), bArray[bOffset]);
         } catch (CryptoException e) {
             ISOException.throwIt(e.getReason());
         } catch (ClassCastException e) {
             ISOException.throwIt((short) 0xE006);
        public static void install(byte[] bArray, short bOffset, byte bLength) {
         new Applet(bArray, bOffset, bLength);
        public void process(APDU apdu) {
         apdu.setIncomingAndReceive();
         byte buf[] = apdu.getBuffer();
         if (selectingApplet()) {
             Util.setShort(buf, (short) 0, DecKeys.VERSION_INFO_MAJOR_MINOR);
             apdu.setOutgoingAndSend((short) 0, (short) 2);
             return;
         try {
             switch (buf[ISO7816.OFFSET_INS]) {
             case (byte) INS_SET_COEF_PRIV:
              _ecPrivatKey.setFieldF2M(e1, e2, e3);
              _ecPrivatKey.setA(valA_F2M, (short) 0, (short) valA_F2M.length);
              _ecPrivatKey.setB(valB_F2M, (short) 0, (short) valB_F2M.length);
              _ecPrivatKey.setG(valG_F2M, (short) 0, (short) valG_F2M.length);
              _ecPrivatKey.setR(valR_F2M, (short) 0, (short) valR_F2M.length);
              _ecPrivatKey.setS(valS_F2M, (short) 0, (short) valS_F2M.length);
              _ecPrivatKey.setK(valK_cofactor);
              code = DecKeys.SW_KEY_DEFINE_CURVES;
              break;
             case (byte) INS_SET_COEF_PUB:
              _ecPublicKey.setFieldF2M(e1, e2, e3);
              _ecPublicKey.setA(valA_F2M, (short) 0, (short) valA_F2M.length);
              _ecPublicKey.setB(valB_F2M, (short) 0, (short) valB_F2M.length);
              _ecPublicKey.setG(valG_F2M, (short) 0, (short) valG_F2M.length);
              _ecPublicKey.setR(valR_F2M, (short) 0, (short) valR_F2M.length);
              _ecPublicKey.setW(valW_F2M, (short) 0, (short) valW_F2M.length);
              code = DecKeys.SW_KEY_DEFINE_CURVES;
              break;
             case (byte) INS_SIGN:
              if (!_ecPublicKey.isInitialized()
                   || !_ecPublicKey.isInitialized()) {
                  code = DecKeys.ER_KEY_NOT_INITIALIZET;
              } else {
                  code = GenerateSignature(apdu);
              break;
             default:
              ISOException.throwIt(ISO7816.SW_INS_NOT_SUPPORTED);
         } catch (CryptoException ce) {
             ISOException.throwIt(ce.getReason());
         } catch (ClassCastException e) {
             code = DecKeys.ER_CRYPTO_EXCEPTION;
         } catch (NullPointerException ne) {
             code = DecKeys.ER_NULL_POINTER_EXCEPTION;
         Util.setShort(buf, (short) 0, code);
         apdu.setOutgoingAndSend((short) 0, (short) 2);
        private short GenerateSignature(APDU apdu) {
         byte[] buffer = apdu.getBuffer();
         _sign1.init(_ecPrivatKey, Signature.MODE_SIGN);
         short signLength = _sign1.sign(buffer, (short) 0,
              (short) (buffer[ISO7816.OFFSET_LC] & (short) 0x00FF), scratch,
              (short) 0);
         _sign2.init(_ecPublicKey, Signature.MODE_VERIFY);
         boolean verifiresult = _sign2.verify(buffer, (short) 0,
              (short) (buffer[ISO7816.OFFSET_LC] & (short) 0x00FF), scratch,
              (short) 0, signLength);
         if (!verifiresult) {
             return ISO7816.SW_DATA_INVALID;
         } else {
             return DecKeys.SW_KEY_DEFINE_CURVES;
        }

  • Transfer rules are not exist for ECC Quality source system in BI Dev

    Hi,
    I Connected BI Dev system To ECC Dev and installed the sales, purchasing,... data flow, but here i am not getting the quality data to show the reports, to get Quality data  I established the connection between BI Dev and ECC QA, while installing the transfer rules for the ECC QA data sources there no transfer rules are exist(only some of them exist) in the business content, but all the update rules,... are exist, when i right on the data source say create transfer rules it is proposing App praposal.
    When i select source system as ECC dev while installing the transfer rules i can see all the transfer rules, but when i select source system as ECC QA i can see only some transfer rules.
    only problem with transfer rules(some of them exist), for remaining all objects are properly existing in business content for ECC QA source system.
    Regards,
    chandra

    Hi Fayzrakhmanov
    Thanks for the quick reply. We are not moving the stuff to QA. We are only connecting QA ECC system to BI Dev. We already have datasources moved to ECC QA and created source system for ECC QA in BI Dev.
    The problem is I am not able to get Business Content transful rule for new source system. We I can find some but not all unlike development.
    Help on this would be appreciated.
    Thanks

  • Transporting DataSources in (ECC) problem

    Hi SCN,
    Just wanted to ask if these are only the two important nodes when collecting and transporting an enhanced datasource?
    I am currently transporting datasources from ECC DEV to ECC QAS. When reviewing my datasources in QAS, append structures were not transported.
    - What I did here was to transport datasources from RSA6. I though it would carry all the changes made in the datasource but it was just the active datasources.
    So I collected the datasources again in a new TR; collecting the requests only in one TR (as per discussions in SCN). First is re-activating the append structure; putting it in a new TR, then collecting the active datasource.
    I am just having doubts if I am missing a step since the (Go To -> Object Directory Entry) is not letting me make a new transport inside the extract structure (double clicking the datasource; double clicking the extract structure; then object directory entry), thus, I am not able to collect the standard extract structure table (or is this because the datasource I am transporting is a standard one?).
    Thanks in advance for any assistance you can provide.
    Thanks.

    I always thought that I need to collect it in one TR (Active datasource, Extract Structure and Table Structures). But, it was okay to have the append structure in another TR.
    What I did was to transport the DataSource then followed by the append structure's TR. It's all good now.

  • Changing the ECC Client in DEV affects Transformation?

    Hi,
    I have a Clarification here.
    We have 2 clients for ECC Dev, 300 & 100.  We completed all our developments in BID linking to 300 client.  Now, Customer says that he has more data in 100 client, so he wants to do testing of that data.
    We have activated all the MD & TD Datasources in 300 Client and all the Transformation mappings are also pointing to 300.
    How can this be achieved?  Now, if suppose, Basis changes the Logical system to 100, do i have to do all the Activations in ECC again for 100?  Do I have to create Transformations for all the Targets again?
    Thanks for your time.
    Regards,
    Murali

    Hi Murali,
    Transformations are not source system dependent, when you say that you can see the name of source system in your transformation, where actually you can see that name? In the description or do you have source system as field in the header informaiton of Transformation?
    You can get the difference, when you double click on your Data source you will see the Source system as separate field in the header information, but in case of transformation you will have only source or transformation and Target as important fields along with other fields.
    Or are you saying that in the transformation mapping of fields you have source system ID assigned to target field source system ID?
    And during transport source system changes are taken care by using transport connection, go to your RSA1 transaciton in the target system and go to Transport Connection-----> "Conversion" button on the tool bar here you can do the mapping of your source client and target client.
    Regards,
    Durgesh.

  • Pointing BW DEV Client to a another client in ECC

    Hi Folks,
    I have a questions on BW & Basis.
    We are having multiple clients in Ecc Development
    ECC DEV i.e DE0 100 200 300.
    Our BW Client is pointing to ECC DEV 200.
    Now to ensure data integrity, We want to point the BW Client to DEV 300.
    DEV 300 has only conversions. And the Data in 300 is more accurate.
    And ofcourse, delete the previous master data and transactional data in BW and do the dataloads again in BW.
    Can you advise:
    If this will affect the present development happening in BW. Please note BW its the same client, but pointing to a different client in ECC within the Development Environment.

    Thank You for the responses.
    We are using ECC 200 for BW Extractions. Now BW Dev is pointing to ECC 200 Datasources. But the chart of accounts is completly messed up. Refereshing the data in 200 from 300 will not help as the Chart of Accounts and other issues.
    So We want another client copy of ECC 200 to ECC 300.
    And the functional team wants to do conversions in this new client.
    Our concern, is
    Can we change the pointer of BW DEV to this new ECC Client 300.
    If Yes, will this effect my current development happending in BW.
    Our Development is mostly happending on the reporting side. We completed the Desing of the BW Backend.

  • Error "Problem occured locking WS object" while activating Proxy

    Hi All,
    I have move an Inbout proxy to a different Client(QA system) and in QA system that proxy shows incative.
    When i tried to activate that proxy/service in Sproxy, getting error "Problem occured locking WS object".
    Proxy was active in development system and was working fine without any error.
    Please provide some help, what need to be done to fix this issue
    Thanks
    Harshit

    Hi Harshit,
    Try with the following steps in sequence:
    1. Re-genarate the proxy in Development - Create a New Transport Reuest.
    2. Transport the Proxy from PI Dev to PI OA
    3. Confirm the Proxy in PI QA and then, transport the re-generated Request from ECC Dev to ECC QA.
    Regards,
    Pranav.

  • BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

    Background:
    I am relatively new to BW team and will be going through my 1st source system upgrade.
    We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
    We are upgrading to the source system to ECC 6.0.
    In Development and QA Environments:
    we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
    We have a opportunity to compare the BW Objects, data flow and data loading from
    both source systems.
    In Production, however, we will just upgrade over 3 days downtime.
    One Question that comes to mind in this regard...
    What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
    Some of the suggestions that were given to me include following points.
    Before Upgrade:
    1 Check data, taking pre images of it for testing with post upgrade.
    2. Perform proper analysis of Source system related BW objects.
      - A complete listing of actively used Datasources,.. etc.
    3. Make delta queues empty,
    Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
    4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
    After Upgrade:
    1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
    (depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
    2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
    3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
    Maintain Control Parameters for Data Transfer
    http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
    4. Check for Changes to extract structures in LBWE Customizing Cockpit 
        - OSS Notes 328181, 396647, 380078 and 762951
    5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
    7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc. 
    Below is a link for some useful programs in this regard.
    https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
    6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
    As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
    7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
    new/changed datasources,if needed. 
    8. Check all CMOD enhancements.
    If we are using a customer exit with the extractor in the OLTP, see Note 393492.
    7. Check for unicode (all custom programs or Function Modules for DataSources)
    5.  Check all the queues in RSA7, start delta runs and test data consistency.
    For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
    9. Take back up of data posted during upgrade for contingency planing.
    10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
    Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

    Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
    We have similar scenario -
    We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
    Our strategy in ECC deployment  ->
    In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
    In production we are going to use same system PRXX upgraded from 4.7 to ECC.
    Now we are in testing phase of ECC with all interfaces like BI in Dev.
    My questions are below ->
    How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
    Also in new ECC sourcesystem copy  we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
    Is there any easy way for above scenario ?
    Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
    I have found some other links which have some pieces of information regarding the topic -
    Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
    BI 7.0: Source System upgrade  from R/3 Enterprise to ECC 6.0
    Re: ECC 6.0 Upgrade
    Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
    ECC 5.0 to ECC 6.0 upgrade
    Thanks
    Prasanth

  • Can we have SAP R/3 QAT system as source system  for BI dev

    HI ,
    We are doing SAP BI implementation and in our company we have already SAP R/3
    The problem is BI team is doing some development in BI DEV and they want to see some data.
    But unfortunately we don't have much data in DEV enviornment.
    So my question is can we have SAP R/3 QAT system as source system  for BI dev.
    Will there be any issues going forward.
    As per my understanding technically source system is just an RFC connection for BI, so we can point it to QAT as well.
    Do you guys foresee any issues in that?
    Thanks,
    Sumit

    Hello Sumit,
    What Arun said was what my concern was, he explained exactly the scenario that I faced, and that your BI team will face if you arrange your landscape as you said. 
    In my company for a while I had the BI Dev box connected to our ECC SND box.
    It was done that way because of the lack of data in ECC Dev.
    It worked, but it was definately not the best solution.  Today we have BID and ECC Dev connected, BIQ and ECC Q, and BIP and ECC Prd.  We do have data in teh attached ECC systems due to recent refreshes too, a large data set is very nice as it helps the BI team significantly.
    That is the best way to arrange the landscape (and throw a BI SND to ECC SND for the true best practice!)
    Thanks,
    Nick

  • Could not start the app due to a configuration problem

    Hi Gurus,
    I have an issue to be resolved asap, need your assistance.
    I have implemented SAP Fiori apps (Approve Purchase Order, Approve Purchase Contract, My Leave Request and Approve Leave Request)
    We have only one Gateway system and 3 back end ECC systems.
    Gateway Client 220 is integrated with ECC Dev and performed all the configurations and tested successfully.
    We have created a new client 320 with a copy of client 220, Integrated 320 client to ECC quality system and performed necessary configurations and while testing Approve Purchase order and Approve Purchase Contract tiles are loading the count from ECC Quality system but when I click on the tile it throws an error "could not start the app due to a configuration problem" and when I click the error ot is being redirected to Client 220.
    From the inspect element I found below error
    2015-04-13 12:22:13 INTEROP service's ResolveLink operation returned 2 targets for hash '#PurchaseOrder-approve', first one is used. - used target: {"id":"PurchaseOrder-approve~652","shellType":"FLP","postParameters":"","text":"Approve Purchase Orders","applicationData":"SAPUI5.Component=ui.s2p.mm.purchorder.approve","applicationAlias":"ApprovePurchaseOrders","applicationType":"URL","url":"/sap/bc/ui5_ui5/sap/mm_po_apv"}
    ignored target: {"id":"PurchaseOrder-approve~65k","shellType":"FLP","postParameters":"","text":"Approve Purchase Orders","applicationData":"SAPUI5.Component=ui.s2p.mm.purchorder.approve","applicationAlias":"ApprovePurchaseOrders","applicationType":"URL","url":"/sap/bc/ui5_ui5/sap/mm_po_apv"} sap.ushell_abap.adapters.abap.NavTargetResolutionAdapter
    I did not found any duplicate # key entries in table USOBHASH.
    Any response is highly appreciated, thanks in advance
    Regards,
    Srujan

    Hi Michael,
    Thanks for that, I have raised an OSS message to SAP, to seek their assistance on the solution I followed to fix the issue. I have reverted back the changes and reproduced the issue for SAP guys to investigate further, at last they concluded me there is an external alias defined for /sap/bc/ui5_ui5/sap in transaction SICF in GP1/320, which contains a hard-coded client 220.
    This is responsible for the fact that the services are redirected/opened in client 220
    After removing the client hard-coded in system alaises under /sap/bc/ui5_ui5/ in transaction SICF, I have reverted back the change from "Alternative Logon Procedure" to "standard" in logon procedure of each service and tested, now the issue got resolved.
    This could help someone to resolve the similar issue.
    Thanks everyone
    Regards,
    Srujan

Maybe you are looking for