Inconsitency between transaction PPPM and HRP1001 table

Hi,
I have a scenario where I distribute the data from my HR system to the xRPM system.
Problem as below.
I have 12 qualifications for a partner in the PPM transaction which are in the HR system. Now I check the table HRP1001 and it also shows 12 qualification in the table for this specific Business partner.
Now I delete all the qualification in the transaction PPM for this business partner. Now when I check the table HRP1001 for this business partner I am seeing 6 entries.
How is this possible to have the link between the BP and the Q after I have deleted them in the transaction PPPM. This is looking strange and I am not able to understand the way the system is behaving.
IS this as per the standard or am I missing out something here.
Need all your expert sugesstion here.
Regards,
Vijay V

Hi,
I have found the issue. The issue was with the key date with which I was viewing in the PPPM transaction. Once I set it to 1.1.1980 then it was deleting perfectly.
Closing this thread.
Regards,
Vijay V

Similar Messages

What is the exact purpose of Transaction NACE and NAST Table?

Hi All,
What is the exact purpose of Transaction NACE and NAST Table?
Pls help me
Akshitha.

Hi
When a Output type in an apllication doc is configured with a Medium, Partner, Lang and other communication paramters an entry is created in NAST table
so to trigger the output an entry in NAST is compulsory
Output is a link between the Driver Program and the Sapscript,
An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
Check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
ex-how to config output type.
You will assign output types using Transaction NACE.
Do the follow steps to assign output type
1)Select Application Type V2 which will have description Shipping.
2)Click on Output types button.
3)Go to change mode by pressing Ctrl+F4.
4)Select one output type which already exists
5)Do Copy As(F6)
6)Give your output type against Output Type field.
7)Under General data Tab, Give Program and Form routine and Save the data.
i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
Check the following documentation
In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
If suppose data can be read from EDI then we should go for condition records.
So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
Go to the Transaction NACE.
choose the related sub module.. like billing or shipping
doubel click on Output Types
Choose the Output Type for which whcih you wanted your script to trigger
Then select the Output Type and double click on Processing Routine
Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
Device Types for SAP Output Devices (Detail Information)
Definition
The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
How do I choose the correct device type?
In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
These standard device types are completely defined and need no modification or extension before you use them in device definitions.
You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
Attributes of a Device Type
A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
Reward points for useful Answers

Receivables: Diferrence between "transaction number" and "document number"

Hi!
What is the difference between "transaction number" and "document number" as shown in the transactions window?
Where are they used?
thanks!

Transaction number is the Invoice number. It can be a manually entered number in case of manual invoices. Even in case of imported invoices, it can be a manually assigned number if the trx_number field is populated in the ra_interface_lines_all table. If you Invoice batch source setup indicates automatic transaction numbering, the transaction (invoice) number will be automatically generated sequentially. The starting number is mentioned in the Trx batch source.
The document number is a number which is generated by Document sequencing. To have the document number generated, you have to do few Doc sequencing setups like setting the 'Sequencial Numbering' profile options, creating document sequences and assigning the sequence to the Categories. The trx types are created as categories.
The Transaction number can be the same as the document number if you enable the option 'Copy Document number to Transaction number' in the Invoice batch source.
Hope that helps.
Thanks,
Anil

Difference between transaction currency and document currency.

Hi All,
Would like to know the difference between transaction currency and document currency. If we want to draw both the figures from the GL account, which table can i use?
Thanks,
Mercy

Hey,
Having transaction currency and document curreny in one document would be strange.
Document currency is something you would see in a FI document, whereas transaction currency is part of a CO document.
In finance documents you would talk about document currenty and local currency for instance.
In CO documents, the currency field you can find are transaction currency, object currency en controlling area currency.
In most cases the document currency in FI would be considered the transaction currency in CO. The local currency in FI would be the object currency in CO.
Hope this helps,
Koen

Difference between Data staging and Dimension Table ?

Difference between Data staging and Dimension Table ?

Data Staging:
Data extraction and transformation is done here.
Meaning that, if we have source data in flat file, we extract it and load into staging tables, we take care of nulls, we change datetime format etc.. and after such cleansing/transformation at then end, load it to Dim/Fact tables
Pros: Makes process simpler and easy and also we can keep track of data as we have data in staging
Cons: Staging tables need space hence need memory space
Dimension Table:
tables which describes/stores the attribute about specific objects
Below is star schema which has dimension storing information related to Product, Customer etc..
-Vaibhav Chaudhari

Difference between line type and internal table?

Hi..
I wanted to know, what is the difference between Line type and Internal Table?

Hi,
Before the 4.7 release in SAP if we want to define an internal table we have to write the defination using the occurs statement and we need to define all the fields using INCLUDE STRUCTURE or indidually all the fields ine by one.
From 4.7 release of R/3 SAP introduced the Line type concept and it's part of the ABAP OOPS concept. for internal table defination we don't need to use the occur statements. Instead INCLUDE structure we need to create a Line type for that structure in Se11 and then we can define the internal table like :
DATA : ITAB TYPE TABLE OF <LINE_TYPE>.
Only thing is this table will be a table without header. So for internal table processing we need to define a work area structure of type line of line type . EX:
DATA: WA_ITAB TYPE LINE OF <LINE_TYPE>.
Hope this helps.
Thanks,
Greetson

Error : Transaction header and line tables cannot be empty

please can some one help me.
when i want to create an invoice without anuy line, i have the error : Transaction header and line tables cannot be empty .
can some one tell me how can i solve this
regards.

Hi,
I really don't know if it is possible to create an invoice in AR with no transaction lines. When I interface invoices from another system to AR (and there is no need to detail inventory items), I use a single line with a dummy inventory item or with no inventory item (inventory_item_id and warehouse_id set to null) in transaction lines, and I use the description field to describe the link to the other software in a user-friendly way.
Regards,
Ketter Ohnes
Message was edited by:
Ketter Ohnes

Information on HRP1000 and HRP1001 tables

Hello All,
Could someone please tell me where I can find more information on these tables (HRP1000 and HRP1001 tables) like what they are used for and some documentation? I searched the forums but I did not find much on documentation.
Thanks.
Mithun

Hi Mithun.
I would like to suggest a couple of references,
[SDN - Reference - Which are the best functions to use for reading infotype HRP1000|Which are the best functions to use for reading infotype HRP1000;
[SDN - Reference - HR ABAP - Organisational infotypes |Regarding HR ABAP;
[SDN - Reference - Organizational Model - HRP1000 and HRP1001 |Read the Org Model;
Hope that's usefull.
Good Luck & Regards.

Difference between work area and internal tables.

Hi I wanna know the difference between work area and internal tables.
what happend if i give with out header line in internal table.
also how to assosiate work area to internal table in that scenario.

Hi Balaji..
The internal table is an ABAP runtime object which has two parts the Body and the header.
Whereas a work area cannot have a body.. It is mere a field or group of fields which can hold values at runtime..
In the SAP higher versions mySAP ERP, the use of tables with header line is made obsolete.. But there is absolutely no problem with the same..
Just think that when you define an internal table with occurs or with header line statement, the system automatically creates a workarea with this table, using which you can access the contents in the bosy of tyhe table.. You can read a record from the table body to this header or add a record in the header to the internal table body..
When you work with a table ITAB without a header line, you can not use statements like READ TABLE, APPEND, INSERT etc without giving an explicit work area..
Suppose i have an internal table like:
DATA : itab TYPE STANDARD TABLE OF t001.
This table will not have a header with it.
If you will use APPEND itab. The compilor will give error.
Here i will create a work area with same structure of the table.
DATA : e_wa TYPE t001.
Now i will write:
APPEND e_wa TO itab.
READ TABLE itab INTO e_wa WITH KEY xxxxxx
LOOP AT itab INTO e_wa... etc..
In a better approach we use Field symbols with such tables, instead of structures
FIELD-SYMBOLS: <fs_itab> TYPE t001.
So,
LOOP AT itab ASSIGNING <fs_itab>
READ TABLE itab ASSIGNING <fs_itab> etc.. However we can not use field symbols in few cases..
I hope this will help you..
Thanks and Best Regards,
Vikas Bittera.
**Points for usefull answers**

What is the difference between standard,sorted and hash table

<b>can anyone say what is the difference between standard,sorted and hash tabl</b>

Hi,
Standard Tables:
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Tables:
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique, or non-unique, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Tables:
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.
Regards,
Ferry Lianto

Difference between transaction LT11 and VL06C

Hello,
Could you please let me know difference between transaction LT11 and VL06C ? Whether LT11 can be scheduled in background job in place of VL06C.

Hi..
You are absolutely correct. If u want to set up a background job for TO confirmation u can do it in t-code VL06C...
Apart from that in LT11 you can confirm for a sinle TO only..but in VL06C you have wide options to select the confirmation TOs of deliveries based on Fwd agent..WH nos..picikn/packing staus..etc., Click on All secections(+) option in VL06C to get more selection parameters..
Reg,
JJ
Edited by: Jagsap on Apr 15, 2010 12:59 PM

Difference between transaction CMOD and SMOD in detail

What is the difference difference between transaction CMOD and SMOD in detail
in R3 system.

Hi Vinod,
Transaction CMOD n SMOD are 2 parts of the enhancement. Using SMOD you can search for enhancement and there component. Components includes Function Exit, Function Codes, Program,Calling Screen...so basically all exits.
Using SMOD, if you know the enhancement you can check the available User Exits. For eg. you can find out user exits and corresponding zincludes.
If you know the Exit Name for Eg. Function module exit name you can search the correponding Enhacement name here..which is important for activating exits.
CMOD allows you to create Project for your enhacement. In order to activate every exit code you need to create a project for same and activate it...Eventhough if you write a code and do not create a project for same your exit code will not reflect.
It is mandatory to create and project for exit and activate it.
Hope this will give you good idea about CMOD and SMOD.
Nilesh

Difference between Transaction database and relational database

Whats the Difference between Transaction database and relational database ??

'Transaction' refers to the usage of a database. 'Relational' refers to the way in which a given database stores data.
A 'transaction database' (or operational database) could be relational, hierarchical, et al. A transaction database supports business process flows and is typically an online, real-time system. The way in which that data is stored is typically
based on the application(s). Companies often have multiple 'transaction databases'.
An 'operational data store' (ODS) is an integrated view or compilation of transaction data.
The you get into data warehouse databases, where the transaction data is optimized for querying, reporting, and analysis activities.

Difference between transactions MIGO and MBST

Hi,
Can someone help me understand the difference between transactions MIGO and MBST for Material doc. cancellation ?
Thanks.....

Hi,
As far as movement type 102 is concerned there is no difference in MIGO & MBST.
MIGO is en Enjoy transaction it is a replcement for the trnasactions MB1A,MB1B,MB1C,MBST,MB01 and MB0A etc.
In CIN, excise records are not updated if material document is cancelled with MBST. It will be updated only if it is cancelled with MIGO.
regards,
JP

Difference between transactions RZ10 and RZ11

Can you please tell me the difference between transactions RZ10 and RZ11

Hello Eechaneri,
RZ10 is for profile as well as profile parameter maintainance while RZ11 is for profile parameter display/change.
In RZ11 however you can change only those profile parameters which are dynamic i.e dont need a restart for change. For the ones where restart is needed the value needs to be added/changed in RZ10.
Regards.
Ruchit.

Inconsitency between transaction PPPM and HRP1001 table

Similar Messages

Maybe you are looking for