Attendence Type and Absence Type update

Hi,
When ABSENCES AND ATTENDENCES are entered in CAT2 , the Infotypes 2001 and 2002 (Aabsence info type and Attendence infotype) are not gettting updated.
Can any one please help me with this.
Thanks in advance
Gopi Palleti

Gopi,
First check if the data entry profile with which you entered time needs approval or not? If not, there is a tab in data entry profile settings (CAC1) that will let you do the direct transfer.
If approval is required - make sure time is approved .. again in approvals (CATS_APPR_LITE) you have the option to have the time data directly transferred to HR.
Finally you can use CAT6 to transfer time. Sometimes it does not transfer..I know its wierd .. try with "Repeat Transfer" option in CAT6..
hope this helps..
Regards,
Mark

Similar Messages

Message type and IDoc type to update a sales order

I can create sales order at WE19 by the message type SALESORDER_CREATEFROMDAT2 and IDoc type SALESORDER_CREATEFROMDAT202 . Can I use the same message type and IDoc type to update a sales document (sales order) and also how can I do (I mean, which structures should I use; at E1BPSDHD1X - UPDATEFLAG what should I enter? Put an X to update a document or etsc?)? I enter the "E1BPSDHD1X - UPDATEFLAG" as X, "E1BP_SENDER - LOG_SYSTEM", "E1BPSDITM - ITM_NUMBER", " E1BPSDITM - MATERIAL", "E1BPPARNR - PARTN_ROLE", "E1BPPARNR - PARTN_NUMB" and "E1BPSCHDL - REQ_QTY". The sales order quantity is at "E1BPSCHDL - REQ_QTY" and it is the field that I want to update. When I look at the transaction code BD87, I see the status text as "Enter a document number between 0005000000 and 0005999999". I cannot update the order. How can I update it? Canybody explain me in a detailed manner?
Thanks in advance....
Edited by: Hikmet Akcali on Oct 21, 2009 4:00 PM

At the IDoc type pop-up selection, there are 3 types. These are: ORD_ID01, ORDERS05 and /NFM/ORDERS05. SAP system component version is SAP ECC 6.0 . I choose ORD_ID01. There are structures EDI_Z1, EDI_Z3, EDI_Z5, EDI_Z9 and EDI_Z53. Where should I enter the number of the sales document to be updated? Also, which function module should I choose?
Edited by: Hikmet Akcali on Oct 21, 2009 5:34 PM

Confusion on pair type and Processing Type

Dear Experts
I have the the below doubt in TIP Table
Pair type gives the information on the how the Time pairs being generated as
0-      Non recorded Time
1-      Attendences
2-      Absences
3-      Attendences Recorded from client
Processing Types also gives information on how the Time pairs are coming with below spec
- Pair is deleted at a later stage
BLANK Pair not included in calculation of productive time
P Attendance pair, included in calculation
of planned working time
A Absence pair, included in calculation
of planned working pair
S Planned working time pir
M Overtime pair
Kindly let me know on what senerios we go with pair type and processing type as they have the same meaning
Regards
Giri

Hi Shruit
i am clear but as mentioned in pair type 1= attendence (2011 - Positive) and Planned working time for negative . in processing type S, A,P also signifies the information how the Time pairs are Generated   and also we have Origin indicator of time pair O which specifies wheather the time pairs are coming from E,M.A,P and D.
Since they have same information why Sap has defined pair Type processing Type and Origin Indicator
                                                             I got the inputs theriotically but practically i am not able to get the TIP Table to read and understand .
Thank you very much for the inputs
Giri

Table Types and Line Type

What is the need of Table Types,
when there is Tables.
Even when iam using in the Abap Programs in se38..
iam not getting any difference..
Even i want to about the use of Line type
when there is the structure..
iam sap 4.7 they gave that Table type describe the structure and
functional attributes of an internal table.

Way: 1:
Go to SE84 --> Select ABAP Dict --> Table Types -->
Enter the short names like ORDER wih leading and ending * on the Table Types Field. ---> F8
This will bring all related entries of Table Types(Line Types) having ORDER has a part of its Name.
Way:2:
If you know the Table Name, then go SE11 --> Putch in the Table Name --> Press Display
Now put the cursor on the Table Name field, press CNTLSHFTF3, on the WHERE USED LIST Pop up, Select only the TABLE TYPE Option and press EXECUTE.
This will bring the Table Types and Line Types.
SAP Table Types
I. Transparent tables (BKPF, VBAK, VBAP, KNA1, COEP)
Allows secondary indexes (SE11->Display Table->Indexes)
Can be buffered (SE11->Display Table->technical settings) Heavily updated tables should not be buffered.
II. Pool Tables (match codes, look up tables)
Should be accessed via primary key or
Should be buffered (SE11->Display Table->technical settings)
No secondary indexes
Select * is Ok because all columns retrieved anyway
III. Cluster Tables (BSEG,BSEC) Should be accessed via primary key - very fast retrieval otherwise very slow
No secondary indexes
Select * is Ok because all columns retrieved anyway. Performing an operation on multiple rows is more efficient than single row operations. Therefore you still want to select into an internal table. If many rows are being selected into the internal table, you might still like to retrieve specific columns to cut down on the memory required.
Statistical SQL functions (SUM, AVG, MIN, MAX, etc) not supported
Can not be buffered
IV. Buffered Tables (includes both Transparent & Pool Tables)
While buffering database tables in program memory (SELECT into internal table) is generally a good idea for performance, it is not always necessary. Some tables are already buffered in memory. These are mostly configuration tables. If a table is already buffered, then a select statement against it is very fast. To determine if a table is buffered, choose the 'technical settings' soft button from the data dictionary display of a table (SE12). Pool tables should all be buffered.
Table Types : A table type describes the structure and functional attributes of an internal table in ABAP. In ABAP programs you can reference a table type TTYP defined in the ABAP Dictionary with the command
DATA : itab TYPE TTYP.
Reafer these links below for clear ideas.
http://help.sap.com/saphelp_nw04/helpdata/en/fb/f14736a1f0ad1fe10000009b38f839/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
Thanks
Allot points if this helps!

Diff b/w reference type and elementary type

hi all
can any one what is the diff b/w reference type and elementary type in data element ....
thanks
lokesh

The data type attributes of a data element can be defined by:
Specifying a domain whose attributes are copied by the data element.
Specifying a build-in type where the data type, number of places, and possibly decimal places can be directly specified.
Specifying a reference type, i.e. reference to a class, an interface, a type defined in the Dictionary, a built-in type, or a generic reference to ANY or DATA.
In the maintenance screen you can set the option you require by setting the appropriate flag (domain, built-in type, reference type) and filling in the corresponding input fields.
A reference type is a reference to another type. There are the following kinds of reference types:
Reference to a class or an interface
Reference to a type defined in the Dictionary
Generic reference to ANY, OBJECT, or DATA
Reference to a built-in Dictionary type with specification of the length and possibly also the decimal places
You can use a reference type to define the data type properties for a data element, or for typing the component of a structure or the line type of a table type.
In the field Referenced type, enter the name of a class, an interface, the generic references DATA, OBJECT, ANY, or the name of a type defined in the Dictionary. If the reference type is to be a predefined Dictionary type, choose the reference to the predefined type. Enter the number of characters and, if required, the number of decimal places.
where as
The data class describes the data format at the user interface.
If a table field or structure field or a data element is used in an ABAP program, the data class is converted to a format used by the ABAP processor. When a table is created in the database, the data class of a table field is converted to a corresponding data format of the database system used.
You can find a detailed description of the data classes allowed in the ABAP Dictionary in Overview of the Data Classes.

Automatic determination of Delivery type and Billing type in a sales order

Hi,
I want to know that in a sales order cycle, how does automatic assignment of delivery type and billing type takes place after we create a sales order?
For example,when I create an outbound delivery for a sales order of type normal (OR) then in that case how does the system knows that it has to create an outbound delivery of type LF.How does the system propses it automatically and same is the case of billing document.

Hi
In customising the sales document type (Tcode VOV8) -
specify the default Delivery type in the field DELIVERY TYPE in the 'Shipping' area of the sales document type customisation.
Similarly you can specify the billing type in the BILLING area for both Delivery related billing and Order related billing.
Thanks,
Ravi

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

How to trigger a form based on object type and process type

Hi all,
I am new into SRM.. I have been asked to develop a form by cloning an existing standard form..
Using bbp_output_change_sf badi you can trigger the form by passing the object type but the scenario is such that depending on the object type and process type the new form should be triggered.
The parameter iv_object_type passes the object type but how could i pass the process type ?
In the badi I noticed an import parameter is_event that has a field called transction_type that carries the process type but this field never got populated when i checked using debugger.
Please help as to how i can trigger the form based on the object_type and the process_type.
Thanx in advance.

Thanx again Jay Yang.. Well is there any possibility that you could get the items that were confirmed..
Let me eleborate..
Suppose in the PO u order an item for 10 nos and 5 gets confirmed and u return 2..
Well in my case it is that i need to fill up a field Qty returned / Qty confirmed..
I was able to get the number of items from the PO by passing the the passing the parameter to the FM "bbp_pd_conf_getdetaill"
but i dont know how to get the number of items been confirmed..
The quantity field in the line item structure gives me the number of items returned..
Can u tell me how to get the number of items been confirmed....

Calling Oracle Stored proc with record type and table Type

I have a oracle SP which takes record type and table Type which are used for order management.
Is there anay way to populate parameters with these datatypes and call the stored procedure using ODP.NET?
Please help.
Thanks in advance

Hi,
ODP supports associative arrays and REF Cursors. There is no support for PLSQL table of records.
Jenny

How does a record type and table type works

Hi,
How a record type and table type work for the ref cursor,
below i m giving an example but its giving me errors
can any one help me for this?
declare
type empcurtyp is ref cursor;
type rectype is record (veid t.emp_id%type, vename t.ename%type);
TYPE tabtype IS TABLE OF rectype;
empcv empcurtyp;
vtab tabtype;
begin
open empcv for select emp_id,ename from t;
loop
fetch empcv into vtab;
exit when empcv%notfound;
dbms_output.put_line(vtab.vename||vtab.veid);
end loop;
close empcv;
end;
here we hav table t and i m taking only two fields of the table t which r emp_id and ename.

Hi,
What errors are you getting with this? From experience you don't need a loop to put the records into the ref cursor its usually done on block.
HTHS
L :-)

Oracle Streams 'ORA-25215: user_data type and queue type do not match'

I am trying replication between two databases (10.2.0.3) using Oracle Streams.
I have followed the instructions at http://www.oracle.com/technology/oramag/oracle/04-nov/o64streams.html
The main steps are:
1. Set up ARCHIVELOG mode.
2. Set up the Streams administrator.
3. Set initialization parameters.
4. Create a database link.
5. Set up source and destination queues.
6. Set up supplemental logging at the source database.
7. Configure the capture process at the source database.
8. Configure the propagation process.
9. Create the destination table.
10. Grant object privileges.
11. Set the instantiation system change number (SCN).
12. Configure the apply process at the destination database.
13. Start the capture and apply processes.
For step 5, I have used the 'set_up_queue' in the 'dbms_strems_adm package'. This procedure creates a queue table and an associated queue.
The problem is that, in the propagation process, I get this error:
'ORA-25215: user_data type and queue type do not match'
I have checked it, and the queue table and its associated queue are created as shown:
sys.dbms_aqadm.create_queue_table (
queue_table => 'CAPTURE_SFQTAB'
, queue_payload_type => 'SYS.ANYDATA'
, sort_list => ''
, COMMENT => ''
, multiple_consumers => TRUE
, message_grouping => DBMS_AQADM.TRANSACTIONAL
, storage_clause => 'TABLESPACE STREAMSTS LOGGING'
, compatible => '8.1'
, primary_instance => '0'
, secondary_instance => '0');
sys.dbms_aqadm.create_queue(
queue_name => 'CAPTURE_SFQ'
, queue_table => 'CAPTURE_SFQTAB'
, queue_type => sys.dbms_aqadm.NORMAL_QUEUE
, max_retries => '5'
, retry_delay => '0'
, retention_time => '0'
, COMMENT => '');
The capture process is 'capturing changes' but it seems that these changes cannot be enqueued into the capture queue because the data type is not correct.
As far as I know, 'sys.anydata' payload type and 'normal_queue' type are the right parameters to get a successful configuration.
I would be really grateful for any idea!

Hi
You need to run a VERIFY to make sure that the queues are compatible. At least on my 10.2.0.3/4 I need to do it.
DECLARE
rc BINARY_INTEGER;
BEGIN
DBMS_AQADM.VERIFY_QUEUE_TYPES(
src_queue_name => 'np_out_onlinex',
dest_queue_name => 'np_out_onlinex',
rc => rc, , destination => 'scnp.pfa.dk',
transformation => 'TransformDim2JMS_001x');
DBMS_OUTPUT.PUT_LINE('Compatible: '||rc);
If you dont have transformations and/or a remote destination - then delete those params.
Check the table: SYS.AQ$_MESSAGE_TYPES there you can see what are verified or not
regards
Mette

Idoc types and message types

Hi ,
Anyone can send what are all the std idoc types and message types are there in SAP?
Coz i dnt have SAP.
Please let me know

The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
An IDoc type consists of the following components:
·       a control record
This is identical for each IDoc type.
·       several data records
One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.
·       several status records
These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.
You find various IDOC / Message types in SAP -
http://www.erpgenie.com/sapedi/message_types_masterdata.htm
IDoc Types - Message Types -Accounting Business Processes
IDoc Types - Message Types - HR Business Processes
IDoc Types - Message Types - Logistics Business Processes
Eg.
General       Message types / IDoc types / BAPI
Vendor        CREMAS / CREMAS02
Customer      DEBMAS / DEBMAS03
Accounting   Message types / IDoc types / BAPI
G/L account   GLMAST / GLMAST01
Cost center     COSMAS / COSMAS01
Cost element COELEM / COELEM01

Is there any standard ODS for Contract (value type and quantity type)?

We know that in MM, contract records can be categorized into two different categories, Value type and Quantiy type. We are trying to see if there is any Contract ODS in business content that we can install which can take care of these two types of contract records that we can bring them over to BW from R3?
Thanks

Hi Kevin,
Please see this link,ODS looks related to your requirement.But seems its for CRM and not for MM.
http://help.sap.com/saphelp_nw04/helpdata/en/38/c3813ed9d23e44e10000000a114084/frameset.htm
cheers,
Vishvesh

Message types and idoc types

hi,
     i need the list of message types and idoc types for edi.
      can any one of u pls send it.

Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
           The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
           The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
           The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
           For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
           For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
           The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
           The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
           The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
           The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
           The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
           The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
           The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
           The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
           For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
           For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
           The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
           The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
           The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
           The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
           The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
           This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
           "22" Shipping OK, acknowledgment has yet to come
           "16" Functional acknowledgment positive
           "17" Functional acknowledgment negative
           The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ

Condition Type and Movement Type

Dear all,
Could anyone explain how the relationshipship between condition type and movement type are being maintain?
Example : WE03 and Mvt 101,
WA03 and Mvt 201.
Is there any table or tcodes to view these relationship?
Thank you.

Hi
Both are linked based on the Transaction event type.
for GR movements the transaction even type is WE
For GI Movements the transaction event ype is WA.
Thanks & Regards
Kishore

Attendence Type and Absence Type update

Similar Messages

Maybe you are looking for