Custom step types and custom step data.

Hello.
I have a good understanding of how TestStand allows custom step types to allow users to store custom data.
I have also read numerous posts about users asking for the ability to store some custom data associated with steps.
In my scenario I am required to write a sequence using a few third party supplied step types.
To assist in developing and debugging this sequence, we would like to store a container of custom data with each steps.
Option 1: Create custom step types.
This is really not an option, relying on third party step types. Any customization made to their step types will magically disappear, along with any custom data, the next time I install one of them service packs.
You may argue that I just have to ensure all custom fields are recreated before opening a sequence file. This works in my office when everyone is at edge with this, but in a few months someone will "take responsibility"
and upgrade the 3rd party packs without reading the entire upgrade procedure.
Option 2: Create links in Sequence Locals
This does work, but is not very associative. To work, the name of the Locals entry would need to be the unique ID of the step it refers to.
Also, it requires some more maintenance to insert new steps, and to remove stale references.
I really hope that someone in TestStand R&D reads this, and enables users to store step custom data, for example by adding a "CustomData" container to the TS property of the step.
Regards,
Ivar S.

Ray:
Thanks for answering.
I am aware that I can extend a custom step type by creating a new step type based on the first type.
For example, I have this 3rd party JtagExecuteTest step type, supplied by another solution vendor.
In my sequence, I want a custom error & failure handler, that needs information about each step as they fail.
For handling and logging purposes, I need each step in my sequence to carry information in addition to the setup required by JtagExecuteTest.
So I set forth, and modify the step type JtagExecuteTest step, along with some other 10-15 step types that the other solution vendor has put in their package.
This works like a charm until I have to reinstall or upgrade the package.
Because I modified the steps using their original name, all data I put into the steps are lost.
Next attempt, I follow your advice and create MyJtagExecuteTest step, based on the original steps. Again, I repeat this customization for 10-15 step types.
This works like a charm until I have to upgrade the package.
Now some wise guy at the other solution vendor has renamed a DLL or a function call, breaking down every step that I have customized.
Mush better, though, because I can repeat the customization process and the data does not disappear.
Still, this is just too much hassle just to put TestStand to some decent use.
If I could just click on a step, add my custom properties, and have TestStand retain those data as a user customization that particular step instance.
Much like you have Sequence.Locals, it would be extremely useful to have a Step.Locals container for the users to use at will.
Regards,
Ivar Svendsen.

Similar Messages

Doc type and drilldown Consolidate data transfered from FI

Dear all members,
I config doc type for data realtime update from FI.
But when i run report CX34, doc type of data transfered from FI to EC-CS is blank.
And I can't drilldown this data.
Please show my mistakes
Many thanks,
Orchid
Edited by: Orchid675 on Jul 2, 2010 5:12 AM

Dear Orchid,
in EC-CS the document number and the document type will be new, the doc type info will not be updated so the original FI doc type will disappear.
Typically, in EC-CS all reported financial data (so documents from FI) will be updated with the same doc type at posting level SPACE (realtime update) or 00 (all other).
I hope my question helps.
Ciao,
David

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

Data types and data objects

diff b/w data types and data objects

hi prasanth,
Data Types and Data Objects
Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
Data types are templates for creating data objects. Data types can be defined independently in the ABAP program or in the ABAP Dictionary. As attributes of a data object, data types can also exist in a non-independent state. Data types do not use any memory space for work data, but may require memory for administration information.
As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
A data object is an instance of a data type and occupies as much memory space as its type specifies. An ABAP program only works with data that is available as content of data objects. Data objects are either created implicitly as named data objects, or exanonymous data objects using CREATEDATA.
Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
regards,
sravanthi

[svn] 1455: add sql date types and custom serialization tests

Revision: 1455
Author: [email protected]
Date: 2008-04-29 11:56:59 -0700 (Tue, 29 Apr 2008)
Log Message:
add sql date types and custom serialization tests
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/DateTy pesTest.mxml
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/MyFile Ref.as
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/Proper tyProxyTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/SQLDat eTypesTest.mxml

Congrats to Shanky and Durval!
SQL Server General and Database Engine Technical Guru - June 2014
Shanky
SQL Server: What does Column Compressed Page Count Value Signify
in DMV Sys.dm_db_index_physical_stats ?
DB: "Interesting and detailed"
DRC: "• This is a good article and provides details of each and every step and the output with explanation. Very well formed and great information. • We can modify the create table query with “DEFAULT VALUES". CREATE TABLE [dbo].[INDEXCOMPRESSION](
[C1] [int] IDENTITY(1,1) NOT NULL, [C2] [char](50) NULL DEFAULT 'DEFAULT TEST DATA' ) ON [PRIMARY]"
GO: "Very informative and well formed article as Said says.. Thanks for that great ressource. "
Durval Ramos
How to get row counts for all Tables
GO: "As usual Durva has one of the best articles about SQL Server General and Database Engine articles! Thanks, buddy!" "
Jinchun Chen: "Another great tip!"
PT: "Nice tip"
Ed Price: "Good topic, formatting, and use of images. This would be far better if the examples didn't require the black bars in the images. So it would be better to scrub the data before taking the screenshots. Still a good article. Thank you!"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Steps to create customized Master data infoobjects in BI 7

Hi all,
Can anyone please send the detailed steps to create customized master data infoobject in BI7,and also the data is to be extracted from two different datasources from two different source systems.
Regards,
G.Monica Roja Flora.

Some data modelling tips while creating master data infoobject and extracting data from different source systems -
If there are identical characteristic values describing different objects for the same characteristic in various source systems, you have to convert the values in such a way in SAP BW so as to make them unique.
For example, the same customer number may describe different customers in different source systems.
You can carry out conversion in the transfer rules for this source system or in the transfer routine for the characteristic.
If work involved in conversion is too great, you can compound the characteristic to the InfoObject Source System ID (0SOURSYSTEM). This means it is automatically filled with master data. The Source System ID is a 2-character identifier for a source system or a group of source systems in BW. The source system ID is updated with the ID of the source systems that provides the data. Assigning the same ID to more than one source system creates a group of source systems. The master data is unique within each group of source systems.
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a6399e07211d2acb80000e829fbfe/content.htm
Hope it Helps
Chetan
@CP..

Assignment of Step type and CR step for MDG_S

Hi
This is in continuaton for thread MDG_S workflow.
I original issue which is for MDGS when I assigned WS543000005 to CR type and sumitted CR goes no where,
As as per SWEL it shows No Reciver Found enen though GET_AGENT table is maintained.
In another system I found that WS531000044 is assigned ti CR Type Then I tested it and found that CR creates Work Items also upto final processing.
as per below
Before CR Submission : CR status is 02: Changes to be executed
After CR Submission : CR status is 01:To be considered and Approved
After CR Reviewer approves : CR status is 09: Dependant Data to be processed /Approved
After Purchase reviewer Finalize processing :CR status is 09: Dependant Data to be processed /Approved
After Finainace reviewer Finalixe processing :CR status is 09: Dependant Data to be processed /Approved
Now I can not see CR any where even though CR step 04 and 04 assigned to my user ID
I have some questions as Description in Define Change Request Steps is not Mataching with description in GET_AGENT desesion table.
Also it is observed that step 80 is not assigned to WS531000044 in IMG node Define Change Request Steps but it can be seen in GET_AGENT decesion table and step no 06 and 07 does not appears in GET_AGENT decesion table ( In edit mode).
Can you explain from where assignment of CR steps to CR type in desion table are taken ino accout ?
Why description is not matched for steps under IMG and in decesion table?
Can you explain me releationship between CR step and step type,CR Status and where they \maintained in IMG and how proceeses modelling is diffenent t for determination of Next CR step in case of WS531000044 ?

Please keep in mind that "hard-wired" workflow templates are just that: hard-wired. This means that a specific workflow template (for example WS53100044) will always have the same number of steps, each step will always have the same type and number, agents will always be assigned in the same way, and those can't be altered by configurations. To understand each workflow template's behavior, you can either open that template in transaction PFTC or SWDD, or alternatively, read the exact behavior in SAP Help documentation. You basically need to google the workflow template number and you should be able to find the description of each template's behavior (by the way, the number you type has an extra zero so if you can't find a match on Google, you will know why ).
Now, the assignment of CR steps to CR type is done in the workflow template itself and NOT in the decision table. See the first screenshot:
The step number above "should" correspond to what is in the configuration table (for readability and consistency of documentation purposes). However, if for some reason, it does not, the hard-coded value is the value that will actually be considered. So, in technical terms, the assignment of step numbers in MDGIMG has no influence on how the workflow template will behave. Again, the main purpose is for the corresponding description in the step number configuration table to show on the CR window.
The other thing is the step type. A step type purpose is mainly to indicate what set of buttons will show at the top of the CR window. The fact that step types are represented by numbers confuse a lot of people with step numbers. I would have personally preferred if step types were a 2-char field so that a clear distinction can be made between step types and step numbers. In any case, buttons on the CR correspond to actions and you can see in MDGIMG that you can assign step types to actions. SAP delivers a pre-defined set of step types and associated actions. Those must NOT be altered because they could break the standard workflow templates. However, you can create your own custom step types and link them with as many actions (standard or custom actions) as you like. But again, you can't assign those custom step types to hard-wired workflow templates. You can only use them in your custom workflow templates or in the rule-based workflow.
Now, the question is how does the hard-wired workflow know what step type to use. The answer is easy: you can either find that in the SAP Help documentation or in the workflow template definition in transaction SWDD. For the above screenshot, the step type is 2. You can find that if you double-click the task ID TS75707980 (or display it using transaction PFTC) and look in the "Cntainer" tab. In this case, this task will ALWAYS have type 2. Other tasks are assigned different step types or are more dynamic in the sense that they expect the step type to be passed from the main workflow template calling them. For example TS53200002 will always have type 7, TS60808005 will always have type 5, and TS60807954 accepts the step type dynamically. This last one is the one used in the rule-based workflow (hence it has to read the step type configured in the decision table).
I hope this answers you question. You definitely need some level of workflow design/build knowledge in order to be able to completely understand all of this. Hopefully, this gives you a good starting point.

I need to set up an expense form so that our consultant can "filter" by customer type, program type, and finally the purpose of the trip. For instance: the customer types are churches, schools, organizations. The program type would be fund raising, gift p

I need to set up an expense form so that our consultant can "filter" by customer type, program type, and finally the purpose of the trip. For instance: the customer types are churches, schools, organizations. The program type would be dependent on the customer type selection from the first list. Some examples would be: fund raising, gift planning, surveys, and others. The purpose of the trip would be dependent on the program type selected from the second list. Some examples of trip purposes would be: presentation, design, prospecting. Further, the purpose of trip selection from the third drop-down box would then have to determine the values of other fields by expense type: such as commission, airfare, hotel. etc. I've tried pop-up menu but can't figure out how to "select" from the final popup list and have it populate a field for the purpose of the trip. I've tried to look at the JavaScript examples for dependent drop-down boxes, but can't find any that quite fit what I'm trying to accomplish. I am very new to all of this. No training in writing Javascripts - just trying to wing it. The form has to be very simple for our consultants to use, but also give our office the detail we need to process through the correct account numbers. I would appreciate any detailed step-by-step instructions - kind of a javascript for dummies type of info. HELP!

An AcroForm is the name given to the type of PDF form that you create in Acrobat. An XFA form is the type of form that you create in LiveCycle Designer. Although they are both PDF files, they are very different structurally and have significant;y different scripting models. So pay attention to the information on AcroForms and ignore anything about XFA. Be sure to get the sample PDF forms so you can look at how it works and where the scripts are placed.
What you want to do will require scripting, and if you don't have the experience and are unable to use the information in the tutorials to create what you want, you might consider getting someone who has experience do this for you. I'll often suggest code if I can do so quickly, but what you want requires more than a few minutes.

How to create automatic creation of BP from customer and vendor master data

Hi gurus,
can any one tell how to create automatic creation of BP from customer and vendor master data.
Please give me the steps.
Thanks
Sasikanth.

HI,
Goto SPRO\ Cross application components \ Master data synchronization \ Synchronization control.
Assign account groups of customer and vendors to respective BP grouping. This setting is enough to create BP in background while creating customer / vendor. But the fields groups are very much important, ensure mandatory fields should be sync.
rgds,
Srini

How to use the customer types in customer master data

how to use the customer types in customer master data?
menu path is Extras -> account group info -> customer types

hi,
This is an option given to you to choose (if you need to) the way you perceive this customer.Here you get options including ompetitors,Salespartner, prospect,
default sp ,consumer.
See it helps you to differentiate between prospect(which you may use for quotation or inquiry purpose)Sales partner and the competetor.
I hope this clarifies your quiery.Reward points if so.
Thanking you,
Best regards,
R.Srinivasan

Impacts in COPA of changing material and customer master data

Dear experts,
In my company we are considering following scenario:
Currently mySAPerp 6.0 is implemented for all modules for the mother company.
We have developed a new global template where there are significant changes versus the existing system, especially in the SD processes. Material and customer master also change significantly in terms of content in the tables/fields and/or values in the fields.
The idea was to build the template from scratch in a new machine and roll-out all group affiliates, but now we are considering the possibility of making an evolutionary of the current system and try to stretch it to the processes defined in the global template.
The scenario we want to analyze is: Keeping same organizational structure in terms of Company code, CO area and Operating Concern in existing SAP client and make an evolutionary of the existing settings to the global template processes.
The doubts we are having are the following:
Changing material & customer master data: Impact in COPA
Option 1: Material master data and customer master data codes are maintained but content in the tables/fields is changed substantially, both in terms of logical content of specific fields and/or the values in the specific fields. We have following examples of changes.
Case 1: source field in material master changes logical content. E.g. Material master field MVGR1 is currently used for product series (design line) and the content changes to be the Market Segment. The product series will be moved to a classification field. At least 5 other fields are affected by this. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 2: the source field is not changed so that the logical content of the field remains but the values change, i.e. for the same concept there will be different codifications. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 3: Characteristics where currently the source material master field is a Z field and the derivation is via table look up and where the Z field changes to a classification field. How can you convert the existing COPA line items to ensure that attributes are aligned? Should new characteristics be created or just change the derivation logic of the characteristic?
Option 2: Material master data and customer data codes are re-created (codification of records is changed), meaning that new material and customer codes will exist and content in tables/fields is changed (as in option 1)
Case: material and customer codes are changed. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Iu2019ve never phased a similar scenario and I fear that maintaining operating concern while changing source master data and also SD flows (we have new billing types, item categories, sales doc. Types, order reasons) may lead to inconsistencies and problems in COPA.
I would like to ask you experts if you have come across a similar scenario and if from your experience, it is something feasible to do or there are many risks involved. What can be the impact of this scenario in existing Operating Concern for both option 1 and 2 and what would be the key activities to perform to adapt the existing operating concern. What will be the impact of the needed conversions on P&L reporting?
Sorry for the long story. I hope you can help me out.
Thanks and Regards,
Eric

Hi,
First i think you will need to test if it works for new COPA documents created via billing.
If it works fine then the issue is if you wish to apply these changes to the historical data already posted.
Normally there are transactions like KE4S where you can repost the billing document to COPA
However this may not be viable for bulk postings
You can perform realignment (KEND) but this only works at the PA segment level (table CE4XXXX)
regards
Waman

Customer and Vendor Master Data.

Hi,
Can any body plz tell me how the customer and vendor master data created in real time implementation and the master data's are created by FI CO consultants.
And plz. tell me the procedure
Thank you

Hi
In Real Time Master Data team will look into Creation of the Master data.This will be as same as how you create in a training class.For every external party with whom we do business must be created as a Vendor or a Customer.The system offers seperate functions for maintaining Customer Master Records and Vendor Master Records depending on the requirements of your Organization.
A Complete Customer Account consists of General Data at the Client Level , Company Code Segment and Sales Area Segment.These Data records can be maintained Centrally for all areas or seperately for Financial Accounting and Sales and Distribution.
A Complete Vendor Account consists of General Data at the Client Level , Company Code Segment and Purchase Organization Segment.Vendor Master Records can be maintained Centrally for all areas or seperately for Financial Accounting and Materials Management.
Configuration of Creation of Vendor Master Data Centrally
1.Creation of Vendor Account Groups with Screen Layout -
OBD3
2.Define Screen Layout per Company Code -
OB24
3.Creation of Number Ranges for Vendor Account Groups -
XKN1
4.Assign Number Ranges to Vendor Account Groups -
OBAS
5.Define Tolerance Groups for Vendors and Customers -
OBA3
6.Creation of Vendor Master Data Centrally -
XK01
7.Define Document types and Number Ranges(KR,KZ,KA,KG) -
OBA7
Configuration of Creation of Customer Master Data Centrally
1.Creation of Customer Account Groups with Screen Layout -
OBD2
2.Define Screen Layout per Company Code -
OB21
3.Creation of Number Ranges for Customer Account Groups -
XDN1
4.Assign Number Ranges to Customer Account Groups -
OBAR
5.Creation of Customer Master Data Centrally -
XD01
6.Define Document types and Number Ranges(DR,DZ,DA,DG) -
OBA7
Creation in FI point of view.
Vendor Master Data -
FK01
Customer Master Data -
FD01
Creation in SD point of view.
Vendor Master Data -
VK01
Customer Master Data -
VD01
Creation in MM point of view.
Vendor Master Data -
MK01
Customer Master Data -
MD01
Regards
Venkat

How to transfer SRM PO Condition Type and Custom fields to ECC?

Hi All,
I have a scenario to transfer SRM Line item condition types and few custom fields to ECC.
I have found the following things but structure 'CI_EKPODB' does not exists in ECC.
I am using 'SRM 5.00' and 'SAP ECC 6.0'.
NOTE: I have to transfer condition records when PO is getting created / modified.
1) Earlier I was planning to use BADI 'BBP_CREATE_BE_PO_NEW' in SRM and this will transfer the data to ECC in case of PO
    Creation.
               It contains the Condition fields to be passed to ECC.
But i am unable to implement the same, whenever i create implementation when i click 'Activate' its getting activate then after few seconds its getting deactivate, i think this is because this BADI is not allowed for multiple use and SAP has already made one implementation on the same.
2) I need to implement BADI 'BBP_ECS_PO_OUT_BADI' in SRM and 'BBP_PO_INBOUND_BADI' in ECC.
SRM BADI will pass verified field details to ECC as a custom fields
       It does not contains the Condition fields to be passed to ECC, so i was planning to pass the same as custom field(s).
ECC BADI 'BBP_PO_INBOUND_BADI' will be used to map the fields to correct place and this should work.
i need to modify the structures and pass all the custom fields (z-fields) - (CI_EKPODB but does not exists kindly suggest) as data.
Other required details:
      Transfer of PO does not supported by SAP for service PO's, any suggestion on the same?
Expecting quick reply from your end.
Thanks in advance.
Regards,
Hemant

Naresh,
Thanks for quick response.
My concern is this BADI 'BBP_CREATE_BE_PO_NEW' will trigger only in case of creation, not when PO is changes.
I have to transfer condition types and custom fields to ECC in both the case (create / change)
If i have to do this only in case of creation then i can pass Condition types / custom fields then i can use parameter 'CS_PO1_DOCUMENT' from method 'FILL_PO_INTERFACE1'.
this parameter contains 'IT_POCOND', 'IT_POCONDX' and 'IT_EXTENSIONIN' as parameter so my problem will be solved.
But i dont think this will trigger in both the cases and 2nd thing i cann't implement the BADI since its not marked for multiple use so i am unable to implement the same.
Kindly correct me if i am wrong.
Once again thanks for your reply.
Please suggest on the same.
Regards,
Hemant

Product type and customer details in project

Hi
We are developing a report on the project cost and one of the information in the output should be
Customer ..... Product type .....project defn.... Activity start date end date
My problem is to identify the product type .
The only way i know is to select superior WBSE - setllement rule - select actual settlement- profit segment- open the screen and identify the product type and customer -
All these are sitting in a structure CE00211. Not able to identify in which table i can get it.
Any kind of input is welcome/valuable
Regards
Rudresh

>
Hari Krishna Kudaravalli wrote:
> Hi Rudresh,
>
> Check in CO-PA Tables CEST4 and in CE1S001. Make sure CO-PA should be activated for your Business Scenario. You can get all required details.
>
> Hope this clears you.
>
> Br,
> Hari
Hi Hari
It worked. Thanks
Regards
Rudresh K

Validate Street and House Number in the Customer Master Data (xd01/xd02)

All.
I need to validate if the fields street and house number are in blank in the Customer Master Data transaction (xd01/xd02). I found an user-exit (EXIT_SAPMF02D_001), which I can validate the customer data (KNA1, KNB1, etc) before to save. The problem is in the KNA1 structure, there aren't the fields street (STREET) and house number (NOUSE_NUM1), there is only the field STRAS, which street and house number values are concatenated.I solved this problem using field-symbol to catch these values in the screen, but I know it isn't a good solution. Is there another solution to solve this ? I had problem using this user-exit. It shows a message error type 'E' when either field street or field house number are in blank, after show this message if the user click in the tabs navigator button before press enter button, the transaction shows the error message "System error on reading table DYNTAB, screen no. 0370". Does Somebody know this problem?
Best regards,
Alexandre
ps: I'm coding in the ECC 6.

Amit.
Thanks for your suggestion, but I need to validate these values typed by the user. When I create a customer, I can't get these values in the ADRC table.
Regards, Alexandre

Howto call custom Oracel Data Type with TopLink?

Hello,
in our DB we have a custom Oracle type and a PL/SQL method which uses it.
I would like to call the Oracle data type with TopLink. How can I do this?
I could not find any documentation on this.
I know JPublisher can do this but I don't want to use it!
Please see code below
cheers,
Pete
**************Datatype********************************
CREATE TYPE My_Sub_Object AS OBJECT (Sub_Object_ID Number,
Sub_Object_Txt VARCHAR2(200));
CREATE TYPE My_Sub_Objects AS VARRAY (20) OF My_Sub_Object;
CREATE TYPE My_object AS OBJECT (Object_id Number,
Object_txt VARCHAR2(200),
Sub_Objects My_Sub_Objects);
************PL/SQL-Method*****************************
CREATE OR REPLACE PROCEDURE My_object_pro
(Item_Object out My_Object) is
Item_Sub_Object My_Sub_Object;
Item_Sub_Objects My_Sub_Objects;
Begin
Item_Sub_Object := My_Sub_Object(10, 'Sub Object 10');
Item_Sub_Objects := My_Sub_Objects(Item_Sub_Object);
Item_Sub_Objects.Extend;
Item_Sub_Object := My_Sub_Object(11, 'Sub Object 11');
Item_Sub_Objects(2) := Item_Sub_Object;
Item_Object := My_Object(1, 'Object', Item_Sub_Objects);
End;
/

Object types and Varrays can be used from TopLink stored procedure calls. There was some support for this in 10.1.3, but the support in 11g (preview) is much better. You can also access the JDBC connection from TopLink or your DataSource and use JDBC directly.
In TopLink 11g you can use an ObjectRelationalDescriptor to map the Object type to a Java class, and use this class as the argument type in your StoredProcedureCall.
PL/SQL types are more difficult as they are not supported by JDBC, but your example only includes object types. If you had PL/SQL types you would need to wrap the types in object types, or use a PL/SQL block to convert them. TopLink 11g (preview 3) should have support for these as well.

Custom step types and custom step data.

Similar Messages

Maybe you are looking for