Date Determination using Date Types and Date Rules

Hi Friends,
Iam working on Date Management in CRM 7.0
I have a requirement where I need to calculate the generate the Billing Date present in the Billing Plan tab of the Service Contract.
I have gone through few of the Date Rules defined in the system. My requirement is to subtract the number of days from the Settlement Start Date and populate this Billing Date. It is clear from the existing date rules that we can subtract the days from Settlement Start Date. But I have a new Z field that is created using EEWB, in which user will enter the number of days. Now I need to subtract these days from Settlement Start Date. So, how can I get the reference of this new field. How can I subtract the number of days that the user will enter in this new Z field.
Thanks & regards,
Raju

Hello Robert
I am currently working on service request.I am facing a problem in the date management there.In my service request i have 5 statuses .One of my status is "Pending with consumer".I am using duration settings of service request.By duration settings , i am calculating the duration for which its pending with consumer.I am having 2 response profile one is 24*7 and other is having 9 working hours.In the service request from the SLA configuration i am calculating the escalation date & Time .I need to add the pending with consumer duration with the escalation date and time.I am facing a problem , i am explaining whole problem ..
Let say if the pending with consumer duration is 1440 minutes(that is 24 hours) .I am adding the minutes to the escalation date through the date rule.
I am facing problem that if the service profile is 24*7 then there is no problem but if it is having the 9 hours working service profile then after adding the minutes to it the escalation date is changing to 4 days ahead which is wrong.
I need to add only those minutes for which it is pending with consumer in working hours for the 9 hours service profile
I need to dynamically determine the working hours from the duration then add it to escalation dates when the status is changed from pending with consumer.
Please suggest a badi will work or how to do it.Its urgent as i need to give demo.I will appreciate a quick reply.Please reply

Similar Messages

Problem while changing data for STO Assign Delivery type and checking rule

Hi All,
In Set up STO..... executing Assign delivery type and checking rule.
I am trying to add values to Rule for Adoption of ATP Results in Purchasing(REVFE),Delivery Type for Stock Transfers Within a Company Code(LFART1) and another two more fields..After entering the data When i clik Save button... it shows "Data was Saved".But its not showing when i went back and come
I have checked in debugg mode and table T161V table ..waht ever i entered its not saved in Database table.
We have checked in another system its working fine..
Can anyone please help me on this?

Solved by posting in OSS.
The below include has to be uncommented.
While doing upgrade this include L0ME6F00 has commented INCLUDE L0ME6F99 has uncommented
     view related include-files   (never change, please)        *
*{   REPLACE        CB2K900006                                        2
INCLUDE L0ME6F00.      " subprograms

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 type and Data object

Hi Friends,
        What is the difference between Data type and Data object?
Best Regards,
VRV Singh

hi
good
Each ABAP program define its own data types using the statement.
TYPES dtype TYPE type ...
and declare its own variables or instance attributes of classes using the statement
DATA var {TYPE type} ...
Within the program or a class, you can also define local data types and variables within procedures. Local variables in procedures obscure identically-named variables in the main program or class.
When creating data types and data objects, there are a number of naming convention that also apply for other local program definitions, such as procedures. These are described in detail in the keyword documentation.
The Additions TYPE and LIKE
The additions TYPE type and LIKE dobj are used in various ABAP statements. The additions can have various meanings, depending on the syntax and context.
·        Definition of local types in a program
·        Declaration of data objects
·        Dynamic creation of data objects
·        Specification of the type of formal parameters in subroutines
·        Specification of the type of formal parameters in methods
·        Specification of the type of field symbols
Constructing New Data Types
The TYPE addition allows you to construct new data types in the TYPES, DATA; CONSTANTS; and STATICSstatements. In the TYPES statement, these are local data types in the program. In the other statements, they are attributes of new data objects, meaning that the newly defined data types are not free-standing. Rather, they are linked to database objects.This means that you can refer to them using the LIKEaddition, but not using TYPE.
To construct new data types, the addition TYPE can be used with the following type constructors:
·        Construction of reference types
REF TO type|dobj
·        Construction of structured data types
BEGIN OF struc_type.
END OF struc_type.
·        Construction of table types
tabkind OF linetype
These data types only exist during the runtime of the ABAP program.
Referring to Known Data Types or Data Objects
Using the additions TYPE or LIKE in the TYPESstatement, local data types in a program can be referred to known data types or data objects. This is mainly the case with user-defined elementary data types. If you declare variables using the additions TYPE type or LIKE dobj with statement DATA, the data type of var is already fully defined before the declaration is made.
The known types or data that are referred to must be visible at the point where the data type or variable is declared.
A known data type can be any of the following:
·        A predefined ABAP type to which you refer using the TYPE addition
·        An existing local data type in the program to which you refer using the TYPE addition
·        The data type of a local data object in the program to which you refer using the LIKE addition
·        A data type in the ABAP Dictionary to which you refer using the TYPE addition. To ensure compatibility with earlier releases, it is still possible to use the LIKE addition to refer to database tables and flat structures in the ABAP Dictionary. However, you should use the TYPE addition in new programs.
The LIKE addition takes its technical attributes from a visible data object. As a rule, you can use LIKE to refer to any object that has been declared using DATA or a similar statement, and is visible in the current context. The data object only has to have been declared. It is irrelevant whether the data object already exists in memory when you make the LIKE reference.
·        In principle, the local data objects in the same program are visible. As with local data types, there is a difference between local data objects in procedures and global data objects. Data objects defined in a procedure obscure other objects with the same name that are declared in the global declarations of the program.
·        You can also refer to the data objects of other visible ABAP programs. These might be, for example, the visible attributes of global classes in class pools. If a global class cl_lobal has a public instance attribute or static attribute attr, you can refer to it as follows in any ABAP program:
DATA dref TYPE REF TO cl_global.
DATA: f1 LIKE cl_global=>attr,
       f2 LIKE dref->attr.
You can access the technical properties of an instance attribute using the class name and a reference variable without first having to create an object. The properties of the attributes of a class are not instance-specific and belong to the static properties of the class.
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2ff3358411d1829f0000e829fbfe/content.htm
thanks
mrutyun^

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

Data types and Data object

Can Any one give me Clear definition of Data type and Data objects.
Concept i know clearly.. but unable to explain it..
Regards,
Prasanna

Data consists of strings of bytes in the memory area of the program. A string of related bytes is called a field. Each field has an identity (a name) and 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 an instance of an abstract data type. Data types in ABAP are not just attributes of fields, but can be defined in their own right. There are separate name spaces for data objects and data types. This means that a name can at the same time be the name of a data object as well as the name of a data type.
Data Types:
 As well as occurring as attributes of a data object, data types can also be defined independently. 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 TYPES statement) 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.
 Data types can be divided into elementary, reference, and complex types
Data objects:
 Data objects are the physical units with which ABAP statements work at runtime. Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running. The technical attributes of a data object are its length, number of decimal places, and data type. ABAP statements work with the contents of data objects and interpret them according to their 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.
ABAP contains the following kinds of data objects
Literals
 Named Data Objects
Predefined Data Objects
Dynamic Data Objects

How to use Reference type of Data Element

Hi guys, is there anyone could give me a trace how to use reference type of data element.
More details i'm going to reach is:
I create 2 tables:
eq.
1. table ZFIRST has field X with data element ZFX (Data element i declared).
2. table ZSECOND has field Y.
Here at field Y (second table) I'm going to declare a new data element say it ZFY, but in ZFY I'm going to use the data element as i declared before (ZFX). Is it possible if I do it using reference type data element (SE11)?
I already did this way, but I got error :
Field Y: Reference ZFX to class w/o interface cannot be used in DB table ZSECOND
What does it mean?. Did I miss something about using reference data element type?.
This error occurs when I activate ZSECOND table. However in creating ZFY (reference) to data element ZFX, there is no error occur.
The point is I need to RE-declared existing data element and ot put existing data element(ZFX) to my current table (ZSECOND).
Any helpful will be highly appreciated.
Thanks.
Edited by: dinivian dondi on Nov 4, 2010 8:30 AM

Field Y: Reference ZFX to class w/o interface cannot be used in DB table ZSECOND
What does it mean?. Did I miss something about using reference data element type?.
Apparently system doesn't allow you to type a transparent table field with deep type. This refers to references and tables types as components. The RDBMS (Relational DB Management System) cannot interpret this componenets correclty and mapp them to TABLEs in DB.
So I am affraid you won't be able to type table component with reference to other data element.
The point is I need to RE-declared existing data element and ot put existing data element(ZFX) to my current table (ZSECOND).
Sorry but I don't get it, could you please explain this more clearly. Maybe then we can think of some workaround for you.
Regards
Marcin

Difference between Data carrier type and Data carrier??

Hi experts,
Could you please explain me the difference between Data carrier type and Data carrier with an example??
Regards,
Kiran T

hi Kiran,
Data carrier is to achive communication between server and user front end. We can define one data carrier type along with path as default for all or seperate data carriers type for specific users in define data carrier in SPRO. This defined data carriers again we assign to application in defining network for workstation application in SPRO.
By using data carrier we can upload to & download originals from server. We can change and print the documents from server.
Please award pts if its useful / need further information.
Pramod

Difference Between Data Type and Data Object

Difference Between Data Type and Data Object

hi magesh
Data types can be divided into
elementary,
reference, and
complex types.
Elementary Types
Elementary types are the smallest indivisible unit of types. They can be grouped as those with fixed length and those with variable length.
Fixed-Length Elementary Types
There are eight predefined types in ABAP with fixed length:
Four character types:
Character (C),
Numeric character (N),
Date (D),
and Time (T).
One hexadecimal type:
Byte field (X).
Three numeric types:
Integer (I),
Floating-point number (F)
and Packed number (P).
Variable-Length Elementary Types
There are two predefined types in ABAP with variable length:
STRING for character strings
XSTRING for byte strings
Reference Types
Reference types
describe data objects that contain references (pointers) to other objects (data objects and objects in ABAP Objects).
Data Types
1) As well as occurring as attributes of a data object, data types can also be defined independently.
2)You can then use them later on in conjunction with a data object.
3) The definition of a user-defined data type is based on a set of predefined elementary data types.
4) You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary.
5) You can use your own data types to declare data objects or to check the types of parameters in generic operations.
Data Objects
1)Data objects are the physical units with which ABAP statements work at runtime.
2) The contents of a data object occupy memory space in the program.
3) ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type..
4) 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.
5) 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).
6) 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).
7) As well as fields in the memory area of the program, the program also treats literals like data objects.
hope this helps u,
reward points if useful
Ginni

Differences between DATA TYPE and DATA OBJECTS

I am new to ABAP,I want to know the differences between DATA TYPE and DATA OBJECTS with some examples.
please help me regarding this.

Hi Ashish,
Data Types:       Are pure descriptions.
               No memory is associated with data types.
               Describes the technical properties of data objects.
EX.
1.     C-CHARACTER
2.     D-DATE
3.     F-FLOAT
4.     I-INTEGER
5.     N-NUMERIC TEXT
6.     T-TIME
7.     P-PACKED NUMBER
8.     X-HEXADECIMAL
9.     STRING-Variable length string.
10.     XSTRING-Variable length byte string.
Data Objects: Are created during runtime.
                They cannot exist without the data Types.
                Occupies memory space.
EX:
1.     INTERNAL DATA OBJECT- Internal Data objects
     LITEERAL- A literal has a fixed value.Ex: WRITE:u201DWORK HARDu201D.
     VARIABLES: Data statement is used to create variables.
EX.DATA: NUM TYPE I.
NUM: VARIABLE defined by data statement.
EX: DATA: PRICE LIKE NUM.
     CONSTANT-It is a data object, which contains a constant value throughout the program.
Can be declared in program by using CONSTANT statement.
EX:CONSTANT: INT TYPE I VALUE 15.
2.     EXTERNAL DATA OBJECT: Are defined in tables i.e In ABAP/4 dictionary you can access this data from table.
         EX: TABLES: SFLIGHT
          DATA: SEATS LIKE SFLIGHT-SEATSMAX.
3.     SYSTEM DEFINED DATA OBJECTS:Space & system variables like SY-UNAME,SY-DATUM, SY-REPID.
4.     SPECIAL DATA OBJECTS:
     PARAMETERS: Are Variables ,which can accept value from user.
      SELECTION SCREEN : Are special internal tables to accept value ranges from user.
3 APPROACHES TO DEFINE DATA OBJECTS.
1.     ELEMENTARY TYPES
DATA: Customer _Name (25) TYPE C,
               Vendor_Name (25) TYPE C.
2.     REFRENCE TO AN EXISTING FIELD:
DATA: Customer _Name2 (25) TYPE C,
              Vendor_Name2 (25) LIKE Customer_Name2
3.     REFRENCE TO NON-ELEMENTARY TYPE:
TYPES: T_NAME (25) TYPE C
DATA: CUSTOMER_NAME TYPE T_NAME
               VENDOR_NAME TYPE T_NAME
4.     RECORD-Information in rows & columns.
DATA: BEGIN OF BOOKING,
                                ID (4) TYPE C,
                                FLIGHT_DATE TYPE D,
                                NAME LIKE CUSTOMER_NAME,
                                END OF BOOKING.
You can also look into SAP help for more information.
Regards,
Indu.

Cardinality between Message Type and Data Type

Hi SAP gurus,
Could anyone please tell me the cardinality between the Message Type and Data Type?
Thanks,
Adnan Abbasi

1:1
Sameer

Sales Order VA01 - "No control data for checking group 04 and checking rule

Dear Gurus,
When saving a sales order in VA01, I get the following message: "No control data for checking group 04 and checking rule A"
Can anyone explain to me what that means?
How can I correct this error?
Regards
Chris

Check this thread
[Re: Process Order Material availability check error|Re: Process Order Material availability check error;
thanks
G. Lakshmipathi

OTL I am trying to wright a SQL query that will return the date the timesheet was submitted and date/time it was approved, can anyone guide me on this?

Hi
I am trying to wright a SQL query that will return the date the timesheet was submitted and date/time it was approved, can anyone guide me on this?
I basically need person name who submitted, date - time it was submitted for approval, then the person who approved it and the date - time that it was approved
Thanks
Ruby

Ruby,
you can start with HXC_TIMECARD_SUMMARY table for submitter detail. But for approver details, i think you need WF tables to get the data for item type HXCEMP.

Could you check our source? (To determine the PR type and number range)

Hello.
We use SRM Server5.5 with Classic Scenario.
We will use the BADI BBP_SC_TRANSFER_BE to determine the PR type and number range according to your recommend.
We have two PR type in R/3.
1) KGPR
2) KTR1
As you know that shopping cart has no type. So we add customer field to mapping to R/3 PR type and this field has two values.
1) PR01: mapping to KGPR
2) PR02: mapping to KTR1
We will use the method GROUP_RQ to determine the PR type.
If customer field is PR01, PR type is determined KGPR
If customer field is PR002, PR type is determined KTR1.
To determine the PR number range, we will use the method GET_NUMBER_OR_RANGE.
If PR type is KGPR, Choose the No key 12
If PR type is KTR1, Choose the No key 16.
Configuration step:
1. Maintain the PR number range in SRM.
No key: 12 (for KGPR) internal NR
No range: 2520000000 2529000000
No key: 16 (for KTR1) internal NR
No range: 2560000000 2569000000
2. Maintain the PR number range in R/3
No key: 12 (for KGPR) Ext NR
No range: 2520000000 2529000000
No key: 16 (for KTR1) Ext NR
No range: 2560000000 2569000000
3. Assign the PR number range to PR type in R/3
KGPR 12 (EXT)
KTR1 16 (EXT)
4. Maintain the attribute in SRM
Document type in R/3
 Add KGPR and KTR1
We developed this logic, but its not working.
LOOP AT ct_proc_item INTO ls_proc_item Where is no date in ct_proc_item:
We can not find out the reason.
Could you check our source?
METHOD if_ex_bbp_sc_transfer_be~group_rq.
DATA:
 ls_proc_item TYPE bbps_procurement,
 lv_number_int TYPE bbp_item_no,
 ls_item TYPE bbp_pds_transfer_item,
 lv_group_counter TYPE numc5,
CONSTANTS:
 lc_on(1) VALUE 'X'.
SORT ct_proc_item BY obj_to_gen.
CLEAR: lv_group_counter.
LOOP AT ct_proc_item INTO ls_proc_item
where obj_to_gen eq iv_object_to_generate.
get item data which includes customer fields
 MOVE ls_proc_item-preq_item TO lv_number_int. " convert
 READ TABLE it_item INTO ls_item WITH KEY number_int = lv_number_int.
 IF sy-subrc = 0.
 IF ls_item-pr_type EQ 'PR01'.
 ls_proc_item-doc_type = 'KGRP'.
 ELSEIF ls_item-pr_type EQ 'PR02'.
 ls_proc_item-doc_type = 'KTR1'.
 ENDIF. " lv_cust_field
 lv_group_counter = lv_group_counter + 1. " increase counter
 ls_proc_item-group_1 = lv_group_counter.
 MODIFY ct_proc_item FROM ls_proc_item
 TRANSPORTING group_1.
 ENDIF. " sy-subrc
ENDLOOP.
cv_method_active = lc_on.
ENDMETHOD.
method IF_EX_BBP_SC_TRANSFER_BE~GET_NUMBER_OR_RANGE.
if is_item-pr_type = 'PR01'.
 CV_NUMBER_RANGE = '12'.
 CV_NUMBER = '2520000000'.
elseif is_item-pr_type = 'PR02'.
 CV_NUMBER_RANGE = '16'.
 CV_NUMBER = '2560000000'.
endif. " is_proc_item / is_item
Thank you
Best Regard
SH

Hi
Please find some suitable sample code, which might help you out.
method IF_EX_BBP_SC_TRANSFER_BE~GET_NUMBER_OR_RANGE .
* IV_OBJECT_TO_GENERATE
* '1' Reservation
* '2' Purchase Requsition (BANF)
* '3' Purchase Order
* '4' Customer Object
* 1. current item data are in structures
* - IS_ITEM shopping cart item data including Customer Fields
* - IS_PROC backend relevant item purchasing data
* 2. accounting data in tables
* - IT_ACCOUNT all shopping cart account. data with Customer Fields
* - IT_PROC_ACCOUNT backend relevant accounting data for current item
* - key criteria between this tables are
* - it_proc_account-preq_item
* -serial_no (numc 2)
* - guid from is_item
* - it_account-p_guid
* -accno(numc 4)
* A) example to use current item data + item customer fields
* if is_proc_item-DOC_TYPE = 'ABCD' AND
* is_item-<field of CI_BBP_ITEM> = .
* set own number range
* CV_NUMBER_RANGE = .
** set own number
** .. ==> if initial SAP Standard with no.range will be processed
* CV_NUMBER = .
* endif. " is_proc_item / is_item
* B) example to use only proc_account no accounting customer fields
*data:
* ls_proc_account type bbp_bapipogna.
* loop at it_proc_account
* into ls_proc_account.
* if ls_proc_account-BUS_AREA = '9988'.
** set own number range
* CV_NUMBER_RANGE = .
** set own number
** .. ==> if initial SAP Standard with no.range will be processed
* CV_NUMBER = .
* endif. " ls_proc_account
* endloop.
* C) example to use only accounting customer fields, no other accounting
*data:
* ls_account type bbp_pds_acc.
* loop at it_account
* into ls_account
* where p_guid = is_item-guid.
* if ls_account-<field of CI_BBP_ACC> = .
** set own number range
* CV_NUMBER_RANGE = .
** set own number
** .. ==> if initial SAP Standard with no.range will be processed
* CV_NUMBER = .
* endif. " ls_account
* endloop.
* D) example to use proc_account + customer fields for accounting
*data:
* lv_serial_no type bbp_bapipogna-serial_no, " sequence num 2
* lv_acc_no type bbp_pds_acc-acc_no, " sequence num 4
* ls_proc_account type bbp_bapipogna,
* ls_account type bbp_pds_acc.
* loop at it_proc_account
* into ls_proc_account.
* move ls_proc_account-serial_no to lv_acc_no.
* read table it_account
* into ls_account
* with key p_guid = is_item-guid
* acc_no = lv_acc_no.
* if sy-subrc = 0.
** if ls_account-<field of CI_BBP_ACC> = .
** set own number range
** CV_NUMBER_RANGE = .
** set own number
** .. ==> if initial SAP Standard with no.range will be processed
** CV_NUMBER = .
** endif. " ls_account
* endif. " sy-subrc
* endloop.
endmethod.
method IF_EX_BBP_SC_TRANSFER_BE~GROUP_RQ .
* 1. current item data are in structures
* - IT_ITEM all shopping cart item data including Customer Fields
* - IT_PROC_ITEM backend relevant item data of current log.system
* key criteria between this tables are:
* - IT_ITEM-NUMBER_INT (numc 10)
* - IT_PROC_ITEM (numc 5)
* 2. accounting data in tables
* - IT_ACCOUNT all shopping cart account. data incl. Customer Fields
* - IT_PROC_ACCOUNT backend relevant accounting data for current item
* - key criteria between this tables are
* - it_proc_account-preq_item (numc 5)
* -serial_no (numc 2)
* - is_item-guid
* -number_int (numc 10)
* - it_account-p_guid
* -accno(numc 4)
constants:
 lc_on(1) VALUE 'X'.
* A) example to use only proc_item with NO customer fields
* group requisitions by backend document type
*data: lv_doc_type TYPE esart,
* ls_proc_item type BBPS_PROCUREMENT,
* lv_group_counter type numc5.
* clear lv_group_counter.
* clear lv_doc_type.
* SORT ct_proc_item BY obj_to_gen doc_type.
* LOOP AT ct_proc_item
* into ls_proc_item
* WHERE obj_to_gen EQ iv_object_to_generate.
** new group criteria?
* if lv_doc_type ne ls_proc_item-doc_type. " backend doc.type
* lv_group_counter = lv_group_counter + 1. " increase counter
* lv_doc_type = ls_proc_item-doc_type. " save criteria
* endif.
* ls_proc_item-group_1 = lv_group_counter.
* modify ct_proc_item from ls_proc_item
* transporting group_1.
* ENDLOOP.
* B) example to use item customer fields
* data:
* ls_proc_item type BBPS_PROCUREMENT,
* lv_cust_field type <field of ci_bbp_item>.
* lv_number_int type BBP_ITEM_NO,
* ls_item type BBP_PDS_TRANSFER_ITEM.
* clear lv_group_counter.
* clear lv_cust_field .
* SORT ct_proc_item BY obj_to_gen.
* LOOP AT ct_proc_item
* into ls_proc_item
* WHERE obj_to_gen EQ iv_object_to_generate.
** get item data which includes customer fields
* move ls_proc_item-preq_item to lv_number_int. " convert
* read table it_item
* into ls_item
* with key number_int = lv_number_int.
* if sy-subrc = 0.
** new group criteria?
* if lv_cust_field ne 'XYZ'.
* lv_group_counter = lv_group_counter + 1. " increase counter
* lv_cust_field = ls_item-<field of ci_bbp_item>."save criteria
* endif. " lv_cust_field
* ls_proc_item-group_1 = lv_group_counter.
* modify ct_proc_item from ls_proc_item
* transporting group_1.
* endif. " sy-subrc
* ENDLOOP.
* C) example to use accounting data with customer fields
* group requisitions by backend document type
*data: lv_doc_type TYPE esart,
* ls_proc_item type BBPS_PROCUREMENT,
* lt_account type BBPT_PD_ACC,
* ls_account type bbp_pds_acc,
* ls_item type BBP_PDS_TRANSFER_ITEM,
* lv_number_int type BBP_ITEM_NO,
* lv_account_flag type c,
* lv_group_counter type numc5.
* clear lv_group_counter.
* clear lv_doc_type.
* SORT ct_proc_item BY obj_to_gen doc_type.
* lt_account[] = it_account[].
* SORT lt_account BY p_guid acc_no.
* LOOP AT ct_proc_item
* into ls_proc_item
* WHERE obj_to_gen EQ iv_object_to_generate.
** get accounting customer fields for this item
* clear lv_account_flag.
** ..first get item guid
* move ls_proc_item-preq_item to lv_number_int.
* read table it_item
* into ls_item
* with key number_int = lv_number_int.
* if sy-subrc = 0.
* loop at lt_account
* into ls_account
* where p_guid = ls_item-guid.
* if ls_account-<field of CI_BBP_ACC> = .
* lv_account_flag = lc_on.
* endif.
* endloop.
* endif. " sy-subrc it_item
** new group criteria?
* if lv_doc_type ne ls_proc_item-doc_type OR " backend doc.type
* lv_account_flag = lc_on. " accounting
* lv_group_counter = lv_group_counter + 1. " increase counter
* lv_doc_type = ls_proc_item-doc_type. " save criteria
* endif.
* ls_proc_item-group_1 = lv_group_counter.
* modify ct_proc_item from ls_proc_item
* transporting group_1.
* ENDLOOP.
* !!!! set flag that BADI was processed
* .. ==> no SAP Standard grouping will be processed
 cv_method_active = lc_on.
endmethod.
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Help in using record type and object type

Hi Experts,
I am new to object types and record types.
I want to return the output of this query using one OUT parameter
from the procedure using RECORD type or OBJECT type.
with out using refcursor.
SELECT empno,ename,sal FROM emp WHERE deptno=30;
Let us assume the query is returning 50 records.
I want to send those 50 records to OUT parameter using record type or object type.
Please provide the for the requirement code using RECORD TYPE and OBJECT TYPE separately.
Your earliest response is appreciated.
Thanks in advance.

Hi All,
I have tried this.But it ising not work
CREATE OR REPLACE PACKAGE maultiplevalues_pkg
IS
TYPE t_record IS RECORD
(empno emp.empno%TYPE,
ename emp.ename%TYPE,
sal emp.sal%TYPE);
V_RECORD t_record;
TYPE t_type IS TABLE OF V_RECORD%TYPE;
PROCEDURE maultiplevalues_pROC(p_deptno IN emp.deptno%TYPE,
dept_result OUT t_type);
END;
CREATE OR REPLACE PACKAGE body maultiplevalues_pkg
IS
PROCEDURE maultiplevalues_pROC(p_deptno IN emp.deptno%TYPE,
dept_result OUT t_type)
is
begin
dept_result :=t_type();
for I in(
select EMPNO,ENAME,SAL from EMP WHERE deptno=p_deptno
LOOP
dept_result.extend;
dept_result(i).empno :=i.empno;
dept_result(i).ename :=i.ename;
dept_result(i).sal :=i.sal;
END LOOP;
END;
END;
Please help me OUT return multiple values through single OUT variable in a procedure.
Thanks.

Organtisational data determination for transaction type

Hi!
We are implementing the organizational data determination.
The idea is to fix a specific org unit for several transaction types, because they will always use this unit.
In order to achieve this, we have implemented Org data determination with rule 14000146, Org. Unit Using Transaction Type.
Within the rule, in tab Container, I could assign 1 transaction type. How can I define more? And where do I determine the Org Unit it the rule should determine?
Best regards,
Cristina

hi Cristina
you need to enhance that rule
just copy the rule to Z rule and then create containers specifying the different transaction type in the same way the original transaction is there,
else you need not do this because it is the standard behavior of rule,for every transaction type u just assign the org data profile,it will work the way u want from this
and regarding ur question"where do I determine the Org Unit it the rule should determine"
the rule will automatically determine the org unit,because inside the container the org attributes are used, its like
IN PPOMA_CRM, choose your Organization Unit, Go to tab Attributes, Choose Attribute Maintaineance Scenario as SALES, and below you will be able to view Attribute Transaction Type.
i believe u r using rule for org model
best regards
ashish

Date Determination using Date Types and Date Rules

Similar Messages

Maybe you are looking for