Dependent tables automatic conversion during transport (SE14?)

Hello all,
I have changed the length of our custom ZATLAPC1 attribute of 0MATERIAL from 2 to 3 (data type = NUMC).
When I tried to activate this attribute in the development system - it asked me to go SE14 transaction and convert /BI0/PMATERIAL and /BIC/SZATLAPC1 tables.
So that helped.
But when I transported this change to the test system - the transport failed saying structures changed at field level.
I could only open the system for changes, went to SE14 to convert tables and activate infoobject.
This solution is not really elegant to transport this change to production in order to do manual changes there.
Any one can help me if there is a better option? Is there any possibility the transport will convert dependent tables automatically?

Hi,
when activating your IObj in DEV the system has complained asking you to convert the underlying tables. You should accept this prompt; you will then be directed directly to SE14 where you manually adjust the tables. Then you would have gone back to your RSD1 screen and activate it again. The system would have prompted successively the same for each table to be converted.
If you go by yourself in SE14 (out of RSD1), the "adjustment" won't be "transported automatically".
Usually the transport does that automatically for simple changes. In your case it would have worked if ZATLAPC1 wouldn't have been an attr of your 0MATERIAL I guess; at least in my case, the transport has nearly always taken care of this conversion automatically.
hope this shed some light...
Olivier.

Similar Messages

Transport client dependent table and data

Hi,
How do you add a client dependent table and the entries inside to a transport?
Please help.
Thanks,
John
Edited by: Alvaro Tejada Galindo on Feb 20, 2008 4:33 PM

Hi there!!!
go to Txn SE09, create a request type "Workbench Request".
1 . Go to the Sub task, select the 'Objects' Tab.
2. Enter the Program ID - R3TR
                  Object       - TABU
                  Object Name - (Your Required Table Name)
3. Now Press the Function Button on the right, Enter the Table Key, which is nothing but the value of the primary key fields of row to be sent, typed as one.
eq. to send material number 1 from MARA in client 100, following would be the table key:
100000000000000000001
where first 3 characters are for the client
and the remaining 18 characters are for the material number.
Another simple method would be to-
1. execute Txn se16 and display the required Table Contents.
2. Select the rows to be sent, by selecting the check boxes corresponding to those rows, and then selecting the Menu Option
Menu->Table Entry -> Transport Entries.
3. Create a request.
    the enties would be included in the request.
Hope This solves your Problem. <REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 20, 2008 4:34 PM

Could you pls give the details about the Unicode conversion during Upgrade

Hi,
Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
Waiting for quick response
Best Regards,
Padhy

Hi,
These are the few points i gathered during my upgradation project.
Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
So it is advised to keep a back-up of the existing system.
Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
Version Upgrade involves the following Steps.
Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
First copy the entire E4B system into the E1B System which is created for Version 4.7.
Apply the Version 4.7 CD provided by SAP over the E1B System.
Now check whether all the functionalities that was in E4B system works fine with E1B system also.
Thus the Version Upgrade involves two steps.
1. SAP Upgradation with the help of the CD
2. Manual Upgradation.
1. SAP Upgradation with the help of the CD
This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
2. Manual Upgradation.
This Manual Upgradation involves
2.1 Upgradation of Standard Objects
2.1.1 SPAU Objects
2.1.2 SPDD Objects
2.2 Upgradation of Custom Objects.
Upgradation of Custom Objects can be placed under the following three categories.
Unicode Compliance
Retrofit
Upgrade
Please Find below some of the common Unicode Errors and their solutions
1. Error:
In case of Translate Error; Dangerous use of Translate in Multilingual system.
Correction:
To correct the Error occurring on TRANSLATE statement use this additional statement before the Translate statement.
SET LOCALE LANGUAGE sy-langu.
This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is sy-langu, i.e. the log on language of the user.
2. Error:
In case of Open Dataset Error; Encoding Addition must be included.
Correction:
This Error occurs only when the MODE is TEXT.
To correct the Error occurring on OPEN DATASET statement use this statement instead.
OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
Where: dataset_name NAME OF THE DATASET.
Access INPUT or OUTPUT or APPENDING or UPDATE.
DEFAULT - Corresponds to UTF-8 in UNICODE systems &
NON_UNICODE in NON-UNICODE systems.
3. Error:
In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; Function module UPLOAD is flagged as obsolete.
Correction:
The FM GUI_DOWNLOAD/UPLOAD is used.
The variations to be made in the parameters of the FM:
1. Filename It must be of STRING type.
2. Filetype DAT is not used any longer, instead ASC is used.
3. Field Separator The default value SPACE is used, incase for a TAB separated file X can be used.
4. Error:
In case of CURRENCY/UNIT Addition Error; Use addition CURRENCY/UNIT when outputting.
Correction:
The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
To correct this error follow the following method:
WRITE: /3 'TOTAL',' ', TOTAL.
WRITE: /3 TOTAL, , TOTAL CURRENCY 2. --- Where 2is the Currency Key for Getting 2 decimal places.
5. Error:
In case of TYPE X Error; Variable must be of C, N, D, T or STRING type.
Correction:
We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
So the method to be followed is:-
1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
2. Declare the variable as Type C, and use the method UCCP(XXXX) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute HORIZONTAL_TAB of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
E.g.:
i) *DATA: TAB TYPE X VALUE 09, Tab character
CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
ii) * DATA: CHAR TYPE X VALUE 160.
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA CHAR TYPE C.
CHAR = CL_ABAP_CONV_IN_CE=>UCCP(00AO).
(Here 00A0 is the Hexadecimal equivalent of the decimal 160).
3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
E.g.:
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA : LF(2) TYPE X VALUE 'F5CD'.
DATA : BEGIN OF LF,
A1 TYPE C,
A2 TYPE C,
END OF LF.
LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
6. Error:
In case of the Character -Error; The Character -cant appear in names in Unicode Programs.
Correction:
The Character -(Hyphen) appearing in Variable names is replaced by the character _ (Under Score) for Unicode/Upgrade Compliance.
E.g.:
*wk-belnr LIKE bkpf-belnr,
*wk-xblnr LIKE bkpf-xblnr,
*wk-date LIKE sy-datum,
*wk-wrbtr LIKE bseg-wrbtr,
*wk-name1 LIKE lfa1-name1,
*wk-voucher(8) TYPE c.
wk_belnr LIKE bkpf-belnr,
wk_xblnr LIKE bkpf-xblnr,
wk_date LIKE sy-datum,
wk_wrbtr LIKE bseg-wrbtr,
wk_name1 LIKE lfa1-name1,
wk_voucher(8) TYPE c.
7. Error:
In case of The SUBMIT-TO-SAP-SPOOL Error; you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition.
Correction:
1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
2. Call the FM GET_PRINT_PARAMETERS:
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
3. Use the SUBMIT-TO-SAP-SPOOL statement.
E.g.:
     submit zrppt500
     using selection-set 'AUTO3'
     with res_no eq lo_rsnum
     with sreserv in preserv
     to sap-spool destination p_dest
     immediately 'X'. "print immediate
DATA: print_parameters type pri_params,
archive_parameters type arc_params,
valid_flag(1) type c.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
Submit zrppt500
Using selection-set 'AUTO3'
With res_no eq lo_rsnum
with sreserv in preserv
to sap-spool
SPOOL PARAMETERS PRINT_PARAMETERS
ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
WITHOUT SPOOL DYNPRO.
8. Error:
In case of Message Error; Number of WITH fields and number of Place Holders are not same .
Correction:
Split the statement after WITH into the same number as the place holder for that Message ID.
E.g.:
1. * MESSAGE E045.
MESSAGE E045 WITH '' ''.
2. in program ZIPI0801
     Start of change for ECC6
     message e398(00) with 'Could not find access sequence'
     'for condition type:'
     p_ptype.
message e398(00) with 'Could not find '
'access sequence'
'for condition type:'
p_ptype.
     End of change made for ECC6
9. Error:
In case of Move between 2 different Structures; The structures are not mutually convertible in a Unicode program.
Correction:
Make both the Data Types compatible and then assign the contents.
E.g.:
The statement move retainage_text to temp_text. Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
10. Error:
In case of no description found; add a GUI title.
Correction:
In this type of error gui title is generally missing so add a GUI title to the module pool.
11. Error:
In case of writing internal or transparent table
Correction:
Write individual fields.
E.g.:
WRITE: / EXT. --> EXT should be a character type field
WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
12. Error:
In case of combination reference table/field S541-UMMENGE does not exist
Correction:
Was due to error in reference table S541. TABLE S541 has errors
1)Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)
2)Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)
Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
And that of ZMKCODE (from ZACCODE to ATTR8)
13. Error:
In case of KEY does not exist
Correction:
The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
14. Error:
Incase of WRITE statement, Literals that take more than one line is not permitted in Unicode systems.
Correction: To correct this error, we need to align the spaces accordingly so that the statement doesnt go beyond the line.
15. Error:
Incase of Data statement, The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect..
Correction: To correct this error, instead of like in the Data statement, use type.
16. Error:
Incase of DESCRIBE statement, DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.
Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
CHARACTER MODE is added when the data object is of flat/ character type.
BYTE MODE is added when the data object is a deep structure.
Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
LENGTH clen IN CHARACTER MODE.
Where blen and clen must be of type I.
17. Error:
Incase of DO-LOOP Error, In Do loop range addition needed
Correction:
An internal tables is declared and the two fields (VARYING field and NEXT field) were
Included inside the internal table
E.g.: In program SAPMZP02
DO 11 TIMES
     VARYING STATION_STATE FROM STATION1 NEXT STATION2. ECC6
CASE SYST-INDEX.
WHEN 1
STATION_STATE = STATION1.
WHEN 2
STATION_STATE = STATION2.
WHEN 3
STATION_STATE = STATION3.
WHEN 4
STATION_STATE = STATION4.
WHEN 5
STATION_STATE = STATION5.
WHEN 6
STATION_STATE = STATION6.
WHEN 7
STATION_STATE = STATION7.
WHEN 8
STATION_STATE = STATION8.
WHEN 9
STATION_STATE = STATION9.
WHEN 10
STATION_STATE = STATION10.
WHEN 11
STATION_STATE = STATION11.
18. Error:
Incase of the parameter QUEUE-ID Error, QUEUE-ID is neither a parameter nor a select option in program rsbdcbtc.
Correction:
The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
E.g.: In program Z_CARRIER_EDI_INTERFACE
     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
19. Error:
Incase of EPC Error, Field symbol <TOT_FLD> is not assigned to a field .
Correction:
This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
The OS Note - 1036943 needs to be applied.
Error:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
Correct:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
Error:
Constants : c_tab type x value '09' .
Correct:
Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
Error:
Data : begin of output_options occurs 0 . Include structure ssfcompop.
Data : end of output_options .
Correct:
Data : output_options type standard table of ssfcompop with header line .
Error:
PARAMETERS : NAST TYPE NAST .
Correct:
PARAMETERS : NAST TYPE NAST NO-DISPLAY .
Replace WS_DOWNLOAD and WS_UPLOAD by
GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
Issue:
Moving data from one structure to another structure if those two structures are not compatible
Solution:
we should use move-corresponding or field by filed we need to move it.
If database structures are different in 4.6c and ECC6.0,
Then we should go with append structure concept.
While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
Also Check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
Reward points if helpful.
Regards,
Ramya

Long DDIC Activation for Master Data Change During Transport

Good Morning Folks,
During transport of a change to a custom master data object to production, the data dictionary activation is taking a very long time and using a very large amount of space.
The change to the master data object was adding three additional navigational attributes. This master data is not time-dependant. The master data contains about 1.2 million records and has 49 active navigational attributes u2013 including the three new ones. The Data Dictionary activation is executing report SAPLRSDU for more than 8 hours and is using upwards of 52GB of temp filespace (of 92GB allocated) during this time. To the best of our knowledge, it looks as if it is trying to recreate or repopulate the /BIC/Pxxxx table of the master data. It looks like it's reading billions of records (probably the same 1.2 m records over and over.)
There are no errors in any logs that we can see.
Previous changes to this master data object have been successful, and reasonably fast. And the transport of this change from Dev to our QA environment was very fast.
We still need to get this change in, as well as additional changes that are dependant. Why would this take so long, and is there anything we can do to get this to run faster?
BTW: We are on 3.5 (but looking forward to NW7.)
Thanks, Brian

Brian,
Usually adding nav attributes would mean that the X and y tables get regenerated...
Also do you notice reads only on the P-Table or other tables which have this object as well..?
If it is only the P Table - try refreshing the stats for the same...

Query on view cluster event trigger during transport

Hi SAP Gurus,
I would just like to ask if the subroutines set in events for view clusters would also get triggered upon transport.
We had created a function module which is meant to regenerate a dynamic program when changes are made to a particular table. We're planning to call this function module in a subroutine that is called during an event in the view cluster (set to "before saving the data to database"). However, we would also like for this dynamic program to be regenerated automatically once the table changes are transported to the test/prod systems. Thus, I wondered if setting up the event is sufficient, and that it would also be triggered automatically prior to saving the changes to the database during transport, or if we still need to set up XPRA for this.
Thanks!

Some events are triggered when exportingthe changed data,
- 10 After creating the change request header entries (E071)
- 11 After changing a key entry in the change request (E071K)
- 12 After changing the key entries in the change request (E071K)
which are suitable to add a XPRA entry in the request
But many events (AFAIK those without dialog) are triggered during import (and we can check if the program is called via transaction or import via flag VIM_IMPORT_MODE_ACTIVE, eg. do not execute a form which fill hidden fields like created by and created at.)
Regards,
Raymond

Use of client dependent tables

Hi Gurus,
I have read many threads on difference between client dependent and independent data/objects etc.
But, someone tell me please, wheat exactly the 'Use or Advantage' of client dependent tables/data.
Thanks in advance.
V

HI,
The use of client dependent tables is that if data in one table of a particular client is updated then that data wont be seen in any other clent it provides a security to the data we retrict users with their authorizations in differen clients
When you log on to an SAP System, you log on to a particular client of this system. Any activities you carry out in the system are always carried out in one client. When you plan your SAP system landscape, you must consider which clients you need for which activities.
By assigning activities to be performed in a client, you give each client a particular role. This section describes the most important client roles.
Since you need to adapt the SAP software for your own business needs, each SAP system landscape requires a client where Customizing settings, and possibly ABAP Workbench developments, can be made. This client is known as the Customizing and development client, or Customizing client for short. The abbreviation CUST is used for this client.
Before you can use the Customizing settings and Workbench developments productively, you need to test them extensively for errors. Any faulty settings can seriously disrupt productive operations, and at worst, lead to the loss of productive data. The integrated nature of the various SAP applications means that there are many dependencies between the different Customizing settings. Even an experienced Customizing developer may not discover these dependencies immediately. The correctness of the settings can only be guaranteed with extensive testing. The client where these tests are made is the Quality Assurance Client, QTST for short.
A separate client is required for productive use of the SAP System. So that this client can be used without disruption, it is essential that no Customizing settings or Workbench developments are made here, and also that no tests are carried out. This client is known as the Production Client, PROD for short.
These three clients, CUST, QTST and PROD, are the central clients that exist in every system landscape. Standard system landscapes have precisely one client for each of these client roles.
We recommend that you make all your Customizing settings in a single Customizing client, and then use the CTS to transport them to the other clients.
We also recommend that you do not make any Customizing settings or Workbench developments in the quality assurance or production clients. You can make sure of this by making appropriate client settings.
In addition to the central clients, you can also set up other clients for other tasks. However, you must remember that each extra client takes up additional system resources (main memory and database space). They also need to be administrated. For example, you need to set up and administrate access authorization for the users, and also distribute any changes to other clients with the CTS. You must weigh up the advantages and disadvantages of setting up other clients.
Examples of other client roles are:
Development test client (TEST): Developers can use this client to test their Customizing settings and Workbench developments, before they release their change requests. In this client the developers can create test application data for realistic tests. If they discover errors, they can remove them in the Customizing client. A development test client is always set up in the same SAP System as the Customizing client. This means that any changes that are made to cross-client data in the Customizing client are also immediately visible in the development test client. Changes to client-specific data are copied from the Customizing client to the development test client using a special client copy function. The client copy function uses the unreleased change requests from the Customizing client to do this. The development test client is set so that you cannot make changes to Customizing data and Repository objects.
Prototype or sandbox client (SAND): You can use this client to test any client-specific Customizing settings if you are not sure whether you want to use them in this form. Any settings that you want to keep are then entered in the Customizing client. To prevent conflicts between the prototype client settings and real settings in the Customizing client, you cannot make changes to cross-client Customizing data and Repository objects in the prototype client. The CTS does not record changes made to client-specific Customizing data, and does not transport them from the prototype client. You can make sure of this by making appropriate client settings.
Training client (TRNG): To prepare end users for new functions that are to be transported into the production client, you can set up a training client. The users can use the new functions in this client with specially created application data. This client is set so that you cannot make changes to Customizing data and Repository objects.'''
plzz reward if this information is usefull to u plaa dont forget to reward

Problem during transport

Dear All,
Now i meet a problem during transport my ABAP in dev to prod server. Not sure is BASIS or my problem.
The error is "Request after end mark"
One more question is for the transaction code STMS, the status for production server should be LOCK or IMPORT QUEUE IS OPEN? If it should be IMPORT QUEUE IS OPEN, how i going to do it cos now our status is LOCK?
Thanks for ur help....
regards;
jee

Hi,
The "Request after end mark" will be displayed due to the following:
Requests after the end mark are not imported during the next import. The end mark is automatically deleted only when the next import has completely ended. Afterwards, the requests can be imported. You can see the legend information in the following website:
http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a3847acc11d1899e0000e829fbbd/content.htm
However, as per your questions I understand that the TMS configuration is not proper. Can you check the r3trans and the transport routes/layers again and see what is missing?

Automatic conversions...A Bug? or just a feature(How to turn it off?)

I Using TS 3.0(.0.12373) I seem to have stubbled over a annoying 'feature' which I can't turn off...Any one got ant ideas.......
Every sequence file I load(eg from the \examples\) when When loaded the '*' appears next to the file name indicating a change has happend. When closing the file TS asked "......file modified due to automatic conversions TestStand performed when loading file".
The only change that happened to the .seq file is a change to the Path, timestamps, and Version(From 3.0.0.12373 in the original to 3.0.0.12374 in the Updated one) at certain points in the file (found using a examine differences program ExamDiff.exe) examples below.
Any ideas how this feature is switched on,
and more importantly how to switch it off?
Cheers
Attachments:
rtebeep.seq ‏18 KB
rtebeep_new.seq ‏18 KB

Wojtek -
It appears that somehow you have edited an NI type and incremented the version number. Your debug work was correct, so looking at the sequence file you will notice that the following sections have a changed version number:
[Action]
%VERSION = "3.0.0.12374"
[Error]
%VERSION = "3.0.0.12374"
Basically TestStand assumes that the newly edited NI type superceeds the one the TestStand finds in the sequence file. For most NI types, the default copy is stored in the type palette files and these probably have the 3.0.0.12374 version. Depending on which NI type was edited, a copy of the newly edited type might also be in the INI files that TestStand uses in the Cfg directory.
In TestStand 2.x if a user attempted to
edit an NI type instead of creating your own copy of the type, the sequence editor would warn them and suggest not editing the NI type. In TestStand 3.0, we wanted to be more strict and not allow editing of NI types at all, but the code did not work properly when released and instead it allows anyone to edit NI types without a warning. TestStand 3.1 now propertly prevents the editing of NI types.
What I recommend is to search all INI files under TestStand and all your sequence files for the '%VERSION = "3.0.0.12374"' text and hand edit them to replace this text with '%VERSION = "3.0.0.12373"'. This should address the issue for you.
If you have sent sequence files to others, and you do not want them to see the automatic conversion issue, their files should also be hand edited. Sorry for the inconvenience.
Sincerely,
Scott Richardson (NI)
Scott Richardson
National Instruments

Value conversion during syndication.

Hi All,
I need to do a value conversion during syndication of records out of MDM. The values maintained in my MDM Repository is true and false while the destination system can only read Y and N. What would be the best option to have this value conversion done during the auto syndication?
Appreciate your responses.
- Aditya

One way to handle this is by using key mapping on a lookup table instead of a boolean field. Often times your remote systems will have different internal values than the ones you are storing in your system. For example, you may store "True" or "False" as values in your MDM repository, however ECC doesn't accept those values, instead it wants "X" or "NULL". Likewise, a third-party system may expect "T" or "F". The same thing goes for other fields in your repository (ie: country codes, region values, etc). In cases such as this, you should create a lookup table with key mapping enabled. Then, you can maintain different values based on the remote system. In other words, you may store the value "TRUE" in your lookup table, but the key mapping for true may maintain "X" for ECC and "T" for a legacy system that you define in the console. Then, when you build your syndication map, you may the remote key to the destination field instead of mapping the actual code value of your repository. This way the correct value will always get syndicated to the partner system regardless of what system is being syndicated to.
Does that make sense?

In Pages 5, Maverick, How do I stop automatic conversation of URLs to hyperlinks and seeing them underlined

There used to be a preference setting in Pages. Now it seems gone in Pages 5. So how do I stop automatic conversation of URLs to hyperlinks and seeing them underlined in text. Sometimes I want it, but not always.

The preference setting to turn off links is gone. When you enter content that triggers link detection, a link character style gets applied. Right-click on the link, choose Edit Link from the menu, and then Remove.
To prevent Pages from automatically detecting links, visit Edit > Substitutions > and deselect Smart Links.

I have taken off/turned off iCloud on my mac mini but when I write an email and use contacts it will convert a non iCloud email to and iCloud email automatically. I really don't want this. Any way to stop this automatic conversion?

I have taken off/turned off iCloud on my mac mini (OS 10.8) but when I send an email and use contacts , it will convert the non - iCloud email to an iCloud email automatically. Anyway to stop this automatic conversation?

Robert...
the iCloud webserver wont accept my password for a .mac login, nor will it allow me to change it
See if you can change your password > Apple - My Apple ID
If that doesn't help, launch iTunes on your computer.
From the iTunes menu bar click iTunes / Preferences then select the Advanced tab.
Click: Reset warnings and Reset cache
Click OK.
Restart your computer.
If that that doesn't help...
Moreover, when I try to go into my .mac account on the web,
Delete all apple cookies and empty your browser cache.
See if you can access your account at iCloud.com

Error during Transporting ID objects in PI 7.1

Hello Experts,
I am facing error during transportation of ID objects MY PI is 7.1 version In IR i have exported SWCV it generated .tpz file but in ID if am exporting it is throwing error
Export failed:Internal error during pvc call:Parameter version Specifier or version has the invalid value null
Please suggest me where would be the error any help is highly appreciated
Regards
Praveen

HI,
Problem is with all the folders in Integartion Directory while exporting objects from PI DEV it is throwing error like
com.sap.aii.utilxi.misc.api.ResourceException: Export failed: Internal error during pvc call: Parameter versionSpecifier or version has the invalid value null
     at com.sap.aii.ib.server.transport.impl.utils.PvcUtils.throwRootCause(PvcUtils.java:86)
     at com.sap.aii.ib.server.transport.impl.utils.PvcUtils.createPropagationList(PvcUtils.java:58)
     at com.sap.aii.ibdir.server.transport.impl.service.DirTransportServiceSeImpl.createExportVersionset(DirTransportServiceSeImpl.java:98)
     at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.exportXiObjects(TransportServiceImpl.java:655)
     at com.sap.aii.ib.server.transport.TransportServiceBean.exportXiObjects(TransportServiceBean.java:317)
     at sun.reflect.GeneratedMethodAccessor2467.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:592)
Regards
Praveen
Edited by: Maareddy Praveen Reddy on Nov 1, 2011 11:59 AM

AUTOMATIC PO DURING GR

Hi,
I have done the customization for automatic PO during GR.
The system is creating a purchase order with the Info record price.
Now my question is: Since the cost of the item is totally fluctuating is it technically possible to enter the cost during GR ?
So that the system creates the PO with the cost entered during GR.
I think this is not possible with standard. But would like to have experts opinion.
Regards,
Shakthi.

Hi Shakthi,
Ideally GR is done with material master price....means with the internal valuation exclusive for a plant.
So I dont think the PO conditions will get generated with GR price....
BR,
Krishna

PO document type for automatic PO is transportation module

Hi,
I am generting automatic POs through transportation module. I am able to assign plant, P.org and P. group through transportation planning point for automatic PO but it is always creating PO of NB type. Is there any configuration where I can change the PO type for automatic POs in transportation?
Thanks & Regards,
Yuvnish

Hi
Check the path :-
IMG-->Material Mgt. -->Purchasing --> Define default Values for Document Type.
Regards
Amitesh Anand

Inserting multiple rows in a table automatically

Hello everyone,
A question about SQL/PLSQL.
I have a homework to create a table in SQL and to insert 10,000 rows in the table regardless of what the values are. The question is: is there a way (like a PLSQL code that has a loop) to inserts values in a table automatically without the need to insert the values 10,000 times manually?
I really appreciate it and thanks in advance...

Frank Kulash wrote:
Is it possible to give me an example of a complete Connect BY/Insert statement would look like in my case?See the SQL Language reference manual
http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/statements_9014.htm#i2145081
or your textbook for examples of inserting values with a subquery.
A subquery using dual will work as well as a subquery using any other table; there's nothing about dual or CONNECT BY that complicates using a subquery in an INSERT statement.
If you get stuck, post your best attempt here. If your problem involves an error, then post the complete error message, too.Frank,
Thank you for your help and reply.
I think I did not explain the situation well because what I am looking for is called <b>populating a table</b> and it seems that the CONNECT BY makes a loop of a single column and that is not the case.
I have a table which is called customer and it contains 7 coulmns in which the first one (cust_id) is sequenced as shown below:
create table customers
cust_id int primary key,
f_name varchar2(40),
l_name varchar2(40),
address varchar2(40),
postnr varchar2(40),
city varchar2(40),
e_mail varchar2 (40)
create sequence cust_id
minvalue 0
maxvalue 99999
start with 1
increment by 1
cache 20;Now the quesiton is: how to populate this table with random data of 10,000 rows?
Thank you very much in advanced.

Dependent tables automatic conversion during transport (SE14?)

Similar Messages

Maybe you are looking for