Document Master update - reg

Hi,
I am basically a functional consultant in the process of developing an object to change a Document master of ECM ( CV02N). I am in search of a suitable BAPI to make this change to happen with almost all of the fields available in a Document master with object characteristics also.
Please help me in pointing out a BAPI which will suit my requirement.
Thanks and Regards,

Hi Kevin,
I am not familiar with DMS but please check these programs perhaps they may help.
DMS_KPRO_CONVERT
DMS_KPRO_DELETE.
Regards,
Ferry Lianto

Similar Messages

To make the Billing document header updated with the new VAT number.

Hi Experts
Due the business requirement we change the VAT number of customers for the European countries.
And now how can we ensure that the Billing document header gets updated with the new VAT Reg.Number for the existing Billing documents.
The intention is to ensure that when we Print an already existing invoice,the new changed VAT number should appear in the invoice output.
Please suggest.
Montee

Hi,
   Have these documents been released to accounting? If yes then you have top canecl all the documents to update the billing documents and repost them with the new vat number. I think you might know how VAT gets determined in SAP. If not please go to SPRO-IMG-SD-BF-TAXES-MAINTAIN SALES TAX IDENTIFICATION UMBER DETERMINATION.
1. If the payer has a VAT ID number and RG <> AG, then the tax number
      and tax classification are copied from the payer (in this case, the
      ship-to party is not relevant).
      The tax number is taken according to the 'tax country of
      destination'.
2. If 1. does not apply:
      If the ship-to party has a VAT registration number and the sold-to
      party does not, tax number and tax classification are copied from
      the ship-to party.
3. If 2. does not apply:
      Tax number and tax classification are copied from the sold-to party.
If you enter A, tax number and tax classification are generally copied
from the sold-to party.
The tax number is copied according to the 'country of destination
relevant for taxes'.
If you enter B, tax number and tax classification are generally copied
from the payer.
The tax number is copied according to the 'country of destination
relevant for taxes'.
Kindly please let me know If you need any more information on this.
Regards
Ram Pedarla

Frame Crashes on Save Book After Performing Document Numbering Update

Frame 10 crashes every time when saving book after performing a Format\Document\Numbering update. All of sudden when performing a document "Update" Frame starting generating errors for specific documents in the book. Numbering in docuement does not match numbering for book. So I select those documents generating the error and then do a Format\Document\Numbering and just hit the set button. Then try to save the book and it crashes every time. It crashes for Format\Document\Numbering one document or all of them.

In Frame 7.1/Unix, it is commonly the case that an unrelated crash corrupts the Book's settings for Numbering, although it appears that nothing has changed. It is, of course, a nuisance to reset all the dialogs.
So what I do instead, and which you might try, is to set all of the book number dialogs (all six panes, for each component file) to "Read from File". That seems to be stable and survives crashes. It may or may not fix your problem.

PO created by means of Workflow with out Vendor master updates

Hi Friends,
   I have my scenario like this. I am working with Production server. When ever a request is created, it has to be sent for Vendor master data updates. then only a PO has to be created. The problem is the PO is created and the workflow is completed with out vendor master updates. When i check through SWI6 the step is just skipped. In the graphical view the steps vendor master update i.e tru descion and other wait step types are disappeared. but in the original workflow the steps are present. can any one pls help me in solving this?
Thanks,
Archana.

Hi Arghadip,
Thanks for the reply. The process is like this :
   when once request is created , it will fetch the email id of the approver from LDAP
   Then 2 approval steps are there. first approval is not mandatory. second is mandatory and its having terminatting event.
After this Amendment descion will be there. on rejection of this descion it has to go and update vendor master. Until the amendments the process is going on. after this vendor master update will be there . it includes wait steps to finish the update. then PO has to be created. but from vendor descion to wait event the steps are disappeared when i checked in SWI6 for that user. pls help me.

I want IDOC for Vendor master updation ( XK01 &XK02 )

Hi
I want to do LSMW in IDOC method for this vendor updation.
So I want IDOC for Vendor master updation ( XK01 & XK02 ).
I want to do both create vendor and change also.
Regards,
Ravi
Edited by: kandukuri ravi on Dec 1, 2008 2:56 PM

Hi,
For Vendor Master using IDoc's for LSMW,Use Message Type = CREMAS and Basic Type = CREMAS05.
For Basic type 01,02,03...05 are versions which includes more fields in basic type so better use latest version.
Hope it will help you.
Regards,
Sudhakar Reddy.A

Discuss on Configure Global Shipping Data - "Document Flow Update"

Dear ALl,
I'm recently looking for the solution on some issue, when i use MIGO to post goods receipt with reference to Inbound delivery, but the inbound delivery status always did not been update by the GR.
I would like to understand more details for the below configuration, can anyone please share and advice the details purpose and pros and cons and if this "Document Flow update" is relevant to my issue where the inbound delivery status not updated by the GR?
SRPO: Logistics Execution -> Shipping -> Basic Shipping Functions -> Configure Global Shipping Data --> "Document Flow Update"
Thank you very much,
Regards,
Chee Wee

Unfortunately I am not on ECC 6.0 and I dont see the field that you mention in my system.
There are quite a few links below, which contains some description about this field, of course provided for some issues.
migo with respect to inbound delivery
creating inbound again after goods were rejected
Inbound Delivery Status Update
http://www.sapfans.com/forums/viewtopic.php?f=6&p=985733
http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/link-of-inbound-delivery-and-material-document-3188148
I assume apart from Inbound delivery status updates, other tables like MSEG and document flow tables also gets updated with the inbound delivery number.
Regards,

Material Master Update from group routing.

Dear All,
When we make material routing. in CA02>scheduling>Results--->Update material master (marking). can be done for the lead time scheduling Purpose. and update in CA96.
But when we use Group Routing, and assign multiple materials in routing header, and then go for
CA02>scheduling>Results--->** (no Material Master Update tab Appeared)
Do we have a solution for this?
Thanks & regards
Raghu

Dear,
Follow these steps,
Scheduling in routing (CA02 ) as :
Call up the operation overview for the routing.
Choose Extras-- Scheduling -- Schedule.
You reach the Scheduling dialog box.
Maintain the data on the dialog box. The system proposes Backward scheduling for the scheduling type.
Choose Continue.
You reach the Enter overview variant dialog box 00000001.
Enter the overview variant you want to use to display the scheduling results. Choose Continue.
The routing is scheduled. You reach the Schedule Overview screen containing the scheduling data.
After the scheduling run has been carried out, click on scheduling Result-- update material master
You use this function to update material master. Go to the CA96 and update material master.
Please try and come back.
Regards,
R.Brahmankar

Exit for Material Master UPdate

Hi Friends,
could anyone let me know any user exit for Material Master UPdate.
Thanks in Advance
Regards

hi
good
MGA00001            Material Master (Industry): Checks and Enhancements
MGA00002            Material Master (Industry): Number Assignment
MGA00003            Material Master (Industry and Retail): Number Display
thanks
mrutyun^

Error:-While vendor master update

Hi,
Here issue is at the time of vendor master data update payment method is updated from DMT to DLP .
FK03 >> Environment >> Account changes >> All fields >> All changes
Shows other changes as home address,mobile number etc.
Can anyone tell me why with payment term other changes are coming in change log even if it was not done moreover what could be the possible solution so other changes will not appear in the change log.
Regards,
Dharmesh

Hey!!!
What is the vendor master update error?

Datasource for document master data available?

Hi experts,
I've failed to find extractor for document master data (table DRAW etc.) in R/3 business content. Has anyone found such or do I need to create it all by myself?
I'm on R/3 4.6C and BW3.5
Regards,
Dieter

Hi Dieter,
There is no standard data source on the table DRAW. You would have to create a custom datasource.
Bye
Dinesh

Number document stuck "updating" in icloud

Number document stuck :updating" in icloud. I tried to delete document in my ipad close icloud in ipad and open icloud again but it's not work. I didn't backup my number document, how can i do?

You can back up documents either by downloading them from iCloud.com or from an iOS device by saving to iTunes.
Try turning document and data syncing off on all devices and deleting the problem document, before adding the offending document back change it's name and then re-enable document and data syncing.

Reg Material Master Updation

Dear SAP Genius
is it possible to delete the sales view for a material in material master?
if it's possible how to delete that?
please explain the steps.
Advance thanks.
Regards
Irshath

Dear Kayalan,
1.In standard SAP it is not possible to delete one particular view once after created.
2.The only way in my understanding s setting the deltion flag and carryingout a reoganizing run and create a new material
master for the same.
Regards
Mangalraj.S

Weight change in material master, update all open PO's

Hello
IS there any standard way for mass update open purchase orders, when weights and volumen in material master change ?
example:
there is a change in neto weight for material AAAA, which is inserted into mm02, basic data for his material. This change doesn't effect already created open orders with this material. Is there any standard way to update them in sap 4.7 ?

Changes will get reflected for new docs only. This is standard.
Now other question comes, why you want to change in PO. I am sure PO are already sent to vendor. Then ideally it is not advisable to change in those PO.
If you haven't sent those PO to vendor, open those PO do some minor corrections SAP will populate the change information in PO documents.
Also changed information will get effective later at GR stage also.
So no question to worry.
Check and revert

Controlling segment of FI document not updated through FIDCCP02

hello..
We are using FIDCCP02 basic type for posting FI document from a third party system via XI.
IDOC gets succesfully posted and generates FI document as well (visible in FB03)..it is also showing cost center details in the FI line item as per requirement..
BUT the problem is, while posting the document thru IDOC..<b>it is not updating the controlling document for that Cost Center</b>...though it gets updated when we manually create the FI document.
we checked out the note 114814 , it says that FIDCCP02 does not update controlling component...so use some other IDOC type !!!
now the question is...which basic type / Function module should we use for posting CO details for the FI document ??? and moreover how to incorporate this functionality with the process code i have already developed ( working absolutely fine as far as FI document is concerned )..
please reply to this as soon as possible..
regards
nidhi

<b>Cost Center Accounting</b>
In this activity, you make settings required for distribution in Cost Center Accounting.
There is a difference between settings for distribution method one (centralized Cost Center Accounting), and those for method two (decentralized Cost Center Accounting).
Consistency Check
The function in this section carries out a consistency check of the settings made here. We recommend you use this consistency check to make the relevant settings.
Execute the function in the decentralized systems. Then you can check whether the settings between the systems for the required message types have been correctly maintained.
Double-click on a line in the consistency check log to make the required settings.
You must have maintained the partner profiles in all the systems.
Notes on Overhead Cost Controlling
You make Overhead Cost Controlling settings in Customizing, under Controlling.
The following settings are required to distribute a controlling area:
The distribution method must be defined in the controlling area for the basic data in the "Distribution method" field. You can choose between distribution method one or two.
The logical system name of the central controlling system must be defined in the controlling area for the basic data in the "Logical system" field. The logical system name is defined in the installation and in the client settings. (In IMG under:
Basis Components
Distribution (ALE)
   Sending and Receiving Systems
      Logical Systems
        Assign Logical System to a Client
If you use distribution method two, you also assign all cost centers to a master system, which is the logical system for the cost center.
If you want to use the profit center accounting, read section Distribution scenarios -> Profit Center Accounting
If you want to use profitablitity analysis, read section Distribution scenarios -> Profitablitity Analysis.
Synchronization of settings using the transport system
Some settings for overhead cost controlling need to be in all systems in the same form.
The easiest way to ensure this, is by doing your customizing in a centralized system, and then distributing the data to all systems affected.
The transport system is normally used for the first time that decentralized controlling is provided with customizing data.
For information on compiling the transport orders for decentralized controlling systems, see the Implementation Guide (IMG), under the section on Controlling -> General Controlling -> Productive Start Preparation -> Transport System Settings.
Individual setting synchronization
If you do not make the settings for overhead cost controlling centrally in a Customizing system, but individually in each of the affected systems, then ensure that they all contain the following data in the same form:
Data for all controlling areas:
Currencies
Charts of accounts
Attributes for the controlling area: Basic data
Distribution method
Logical system
Currency type
Currency
Chart of accounts
Fiscal year variant
Standard hierarchy for cost centers
Activated reconciliation ledger indicator
Attributes of the controlling area: Control indicators
Cost Center Accounting activated
Indicator for all currencies
Indicator for company code validation
Assignment of controlling area - company code
Assignmeents between controlling areas and company codes can only be maintained centrally and distributed, if the assignments between local and global company codes match.
Otherwise, you need to make the assignments individually in each system.
The concept of global company codes is explained in Customizing, under the following path:
Predefined ALE Business Processes
    Accounting
      Financial Accounting
Notes on Distributing Plan Prices
Plan prices for the cost center/activity type combination are distributed using the "COACTV" message category. Before you do this, you need to activate the integration for each planning version used and fiscal year.
To do this in the menu Cost Center Accounting,
choose Planning -> Planning aids -> Integration active in
For distribution method one, you need to activate the integration in the centralized system. For method two, you need activate integration in both the centralized and the decentralized systems.
Notes on Distributing the Reconciliation Ledger
When Cost Center Accounting is distributed, you also need to distribute the reconciliation ledger.
If centralized Cost Center Accounting is used in a system other than the centralized general ledger, then you also need to make some more settings in Customizing in addition to the setting for the message flow between decentralized and centralized cost accounting. This is for the distribution of the reconciliation ledger.
The "RCLROL" message dispatch (from decentralized and centralized Cost Center Accounting to the centralized general ledger) must also be inserted in your distribution model with the company code filter object.
You need to maintain these two message flows in the communication parameters.
There is a restriction, whereby reconciliation postings can only be made on company code level.
Distribution Method One: Partner profiles
Partner profiles in the centralized cost accounting system
In the centralized cost accounting system, you need to maintain outbound partner profiles for each decentralized cost accounting system.
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
(RCLROL Roll-up reconciliation ledger
if the centralized system
for the controlling area and
the company code are different)
You need to maintain the inbound partner profiles for the each decentralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different)
Partner profiles in the decentralized cost accounting system
In each decentralized cost accounting system, you need to maintain outbound partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
CODCMT CO-Beleg
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-Up reconciliation ledger
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different).
You need to maintain inbound partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
(RCLROL Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).
Note
The COSCOR (cost centers (core)) and COACOR (activity types (core) message types are obsolete, and should not be used any more. Under no circumstances should they be used with the ZH>COSMAS (cost centers) and COAMAS (activity types) message types.
Distribution Method Two: Partner profiles
Partner profiles in the centralized cost accounting system
You need to maintain outbound partner profiles for each decentralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
CODCMT CO document
(RCLROL Roll-up reconciliation ledger
if the centralized system for
the controlling area and
the company code are different).
You need to maintain the inbound partner profiles for each decentralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
COTOTL Totals records
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system of
the company code,
if the centralized system for
the controlling area and
the company code are different).
Partner profiles in the decentralized cost accounting system
In each decentralized cost accounting system, you need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
COTOTL Totals records
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system for
the company code,
if the centralized system for
the controlling area and
the company code are different).
You need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
CODCMT CO document
(RCLROL Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).
Note
The COSCOR (cost centers (core)) and COACOR (activity types (core)) message types are obsolete and should no longer be used. Under no circumstances should they be used with the COSMAS (cost centers) and COAMAS (activity types) message types.
Error handling
Specifying responsibilities for workflow error processing in the distribution environment.
Workflows are created to problems in cost accounting in the distribution environment. You need to specify employees who are responsible for the errors. You can use ALE-customizing for maintenance:
Basis Components
Distribution (ALE)
    Error Handling
Distribution Method One:
Specifying responsibility in the centralized cost accounting system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSFET_Error COSFET Inbound error
COAFET_Error COAFET Inbound error
CODCMT_Error CODCMT Inbound error
RCLROL_Error RCLROL Inbound error
Specifying responsibility in the decentralized system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSMAS_Error COSMAS Inbound error
COELEM_Error COELEM Inbound error
COAMAS_Error COAMAS Inbound error
COGRP1_Error COGRP1 Inbound error
COGRP2_Error COGRP2 Inbound error
COGRP5_Error COGRP5 Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
Distribution Method Two:
Specifying responsibility in the centralized cost accounting system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSFET_Error COSFET Inbound error
COAFET_Error COAFET Inbound error
COTOTL_error COTOTL Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
CODCMT_Error CODCMT Inbound error
RCLROL_Error RCLROL Inbound error
Specifying responsibility in the decentralized system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSMAS_Error COSMAS Inbound error
COELEM_Error COELEM Inbound error
COAMAS_Error COAMAS Inbound error
COGRP1_Error COGRP1 Inbound error
COGRP2_Error COGRP1 Inbound error
COGRP5_Error COGRP1 Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
CODCMT_Error CODCMT Inbound error
Note
In the distribution model, you must maintain a company code or a controlling area as a filter object for the "RCLROL" message type.
Check consistency
After you have made the settings for distributed Cost Center Accounting, you can check the settings for consistency (see Set up Communication , Partner Profiles, and Check Model Settings).
Cost Center Accounting
In this activity, you make settings required for distribution in Cost Center Accounting.
There is a difference between settings for distribution method one (centralized Cost Center Accounting), and those for method two (decentralized Cost Center Accounting).
Consistency Check
The function in this section carries out a consistency check of the settings made here. We recommend you use this consistency check to make the relevant settings.
Execute the function in the decentralized systems. Then you can check whether the settings between the systems for the required message types have been correctly maintained.
Double-click on a line in the consistency check log to make the required settings.
You must have maintained the partner profiles in all the systems.
Notes on Overhead Cost Controlling
You make Overhead Cost Controlling settings in Customizing, under Controlling.
The following settings are required to distribute a controlling area:
The distribution method must be defined in the controlling area for the basic data in the "Distribution method" field. You can choose between distribution method one or two.
The logical system name of the central controlling system must be defined in the controlling area for the basic data in the "Logical system" field. The logical system name is defined in the installation and in the client settings. (In IMG under:
Basis Components
Distribution (ALE)
   Sending and Receiving Systems
      Logical Systems
        Assign Logical System to a Client
If you use distribution method two, you also assign all cost centers to a master system, which is the logical system for the cost center.
If you want to use the profit center accounting, read section Distribution scenarios -> Profit Center Accounting
If you want to use profitablitity analysis, read section Distribution scenarios -> Profitablitity Analysis.
Synchronization of settings using the transport system
Some settings for overhead cost controlling need to be in all systems in the same form.
The easiest way to ensure this, is by doing your customizing in a centralized system, and then distributing the data to all systems affected.
The transport system is normally used for the first time that decentralized controlling is provided with customizing data.
For information on compiling the transport orders for decentralized controlling systems, see the Implementation Guide (IMG), under the section on Controlling -> General Controlling -> Productive Start Preparation -> Transport System Settings.
Individual setting synchronization
If you do not make the settings for overhead cost controlling centrally in a Customizing system, but individually in each of the affected systems, then ensure that they all contain the following data in the same form:
Data for all controlling areas:
Currencies
Charts of accounts
Attributes for the controlling area: Basic data
Distribution method
Logical system
Currency type
Currency
Chart of accounts
Fiscal year variant
Standard hierarchy for cost centers
Activated reconciliation ledger indicator
Attributes of the controlling area: Control indicators
Cost Center Accounting activated
Indicator for all currencies
Indicator for company code validation
Assignment of controlling area - company code
Assignmeents between controlling areas and company codes can only be maintained centrally and distributed, if the assignments between local and global company codes match.
Otherwise, you need to make the assignments individually in each system.
The concept of global company codes is explained in Customizing, under the following path:
Predefined ALE Business Processes
    Accounting
      Financial Accounting
Notes on Distributing Plan Prices
Plan prices for the cost center/activity type combination are distributed using the "COACTV" message category. Before you do this, you need to activate the integration for each planning version used and fiscal year.
To do this in the menu Cost Center Accounting,
choose Planning -> Planning aids -> Integration active in
For distribution method one, you need to activate the integration in the centralized system. For method two, you need activate integration in both the centralized and the decentralized systems.
Notes on Distributing the Reconciliation Ledger
When Cost Center Accounting is distributed, you also need to distribute the reconciliation ledger.
If centralized Cost Center Accounting is used in a system other than the centralized general ledger, then you also need to make some more settings in Customizing in addition to the setting for the message flow between decentralized and centralized cost accounting. This is for the distribution of the reconciliation ledger.
The "RCLROL" message dispatch (from decentralized and centralized Cost Center Accounting to the centralized general ledger) must also be inserted in your distribution model with the company code filter object.
You need to maintain these two message flows in the communication parameters.
There is a restriction, whereby reconciliation postings can only be made on company code level.
Distribution Method One: Partner profiles
Partner profiles in the centralized cost accounting system
In the centralized cost accounting system, you need to maintain outbound partner profiles for each decentralized cost accounting system.
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
(RCLROL Roll-up reconciliation ledger
if the centralized system
for the controlling area and
the company code are different)
You need to maintain the inbound partner profiles for the each decentralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different)
Partner profiles in the decentralized cost accounting system
In each decentralized cost accounting system, you need to maintain outbound partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
CODCMT CO-Beleg
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-Up reconciliation ledger
in the centralized system for
the company code
if the centralized system for
the controlling area and
the company code are different).
You need to maintain inbound partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
(RCLROL Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).
Note
The COSCOR (cost centers (core)) and COACOR (activity types (core) message types are obsolete, and should not be used any more. Under no circumstances should they be used with the ZH>COSMAS (cost centers) and COAMAS (activity types) message types.
Distribution Method Two: Partner profiles
Partner profiles in the centralized cost accounting system
You need to maintain outbound partner profiles for each decentralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
CODCMT CO document
(RCLROL Roll-up reconciliation ledger
if the centralized system for
the controlling area and
the company code are different).
You need to maintain the inbound partner profiles for each decentralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
COTOTL Totals records
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system of
the company code,
if the centralized system for
the controlling area and
the company code are different).
Partner profiles in the decentralized cost accounting system
In each decentralized cost accounting system, you need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSFET Requesting cost centers
COAFET Requesting activity types
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
COTOTL Totals records
CODCMT CO document
RCLROL Roll-up reconciliation ledger
(RCLROL Roll-up reconciliation ledger,
in the centralized system for
the company code,
if the centralized system for
the controlling area and
the company code are different).
You need to maintain outgoing partner profiles for the centralized cost accounting system for the following message types:
Message type Meaning
COSMAS Cost centers
COELEM Cost elements
COAMAS Activity types
COGRP1 Cost center groups
COGRP2 Cost element groups
COGRP5 Activity type groups
COCOKA Control data object/cost element
COACTV Prices for cost center/activity type
CODCMT CO document
(RCLROL Roll-up reconciliation ledger,
if the centralized system for
the controlling area and
the company code are different).
Note
The COSCOR (cost centers (core)) and COACOR (activity types (core)) message types are obsolete and should no longer be used. Under no circumstances should they be used with the COSMAS (cost centers) and COAMAS (activity types) message types.
Error handling
Specifying responsibilities for workflow error processing in the distribution environment.
Workflows are created to problems in cost accounting in the distribution environment. You need to specify employees who are responsible for the errors. You can use ALE-customizing for maintenance:
Basis Components
Distribution (ALE)
    Error Handling
Distribution Method One:
Specifying responsibility in the centralized cost accounting system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSFET_Error COSFET Inbound error
COAFET_Error COAFET Inbound error
CODCMT_Error CODCMT Inbound error
RCLROL_Error RCLROL Inbound error
Specifying responsibility in the decentralized system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSMAS_Error COSMAS Inbound error
COELEM_Error COELEM Inbound error
COAMAS_Error COAMAS Inbound error
COGRP1_Error COGRP1 Inbound error
COGRP2_Error COGRP2 Inbound error
COGRP5_Error COGRP5 Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
Distribution Method Two:
Specifying responsibility in the centralized cost accounting system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSFET_Error COSFET Inbound error
COAFET_Error COAFET Inbound error
COTOTL_error COTOTL Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
CODCMT_Error CODCMT Inbound error
RCLROL_Error RCLROL Inbound error
Specifying responsibility in the decentralized system
Maintain assignments for the following standard tasks:
Standard task: Identifier Name
COSMAS_Error COSMAS Inbound error
COELEM_Error COELEM Inbound error
COAMAS_Error COAMAS Inbound error
COGRP1_Error COGRP1 Inbound error
COGRP2_Error COGRP1 Inbound error
COGRP5_Error COGRP1 Inbound error
COCOKA_Error COCOKA Inbound error
COACTV_Error COACTV Inbound error
CODCMT_Error CODCMT Inbound error
Note
In the distribution model, you must maintain a company code or a controlling area as a filter object for the "RCLROL" message type.
Check consistency
After you have made the settings for distributed Cost Center Accounting, you can check the settings for consistency (see Set up Communication , Partner Profiles, and Check Model Settings).
reward points if it is usefull ....
Girish

Issue in material master update from presentation server using BAPI....

Hi Guru's...
i am trying to change the material master from presentation server (desktop flat file)
using BAPI(BAPI_MATERIAL_SAVEDATA) ....
while executing my program i am getting the message like material had changed...
but while in mm02 i am un able to fine the updates...
please find below program logic and correct me if any mistakes....
thanks in advance...
*& Report ZAREPAS36
REPORT zarepas36.
DATA : gs_bapimathead             TYPE bapimathead,
       gs_clientdata              TYPE bapi_mara,
       gs_clientdatax             TYPE bapi_marax.
TYPES : BEGIN OF gty_itab1,
        matnr(18),
        matkl(9),
        spart(2),
        ntgew(13),
        gewei(3),
        meins(3),
        END OF gty_itab1.
DATA : gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
       gwa_itab1 TYPE gty_itab1.
TYPES: BEGIN OF gty_itab2,
       abc(132),
       END OF gty_itab2.
DATA: gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
      gwa_itab2 TYPE gty_itab2.
flat file at selection screen
PARAMETERS: p_files TYPE string.
CALL METHOD cl_gui_frontend_services=>gui_upload
EXPORTING
    filename = p_files
    filetype = 'ASC'
CHANGING
    data_tab = gt_itab2
EXCEPTIONS
    OTHERS   = 8.
LOOP AT gt_itab2 INTO gwa_itab2.
IF gwa_itab2-abc(1) = 'S'.
    gwa_itab1 = gwa_itab2-abc(132).
    APPEND gwa_itab1 TO gt_itab1.
ENDIF.
ENDLOOP.
loop at gt_itab1 into gwa_itab1.
*Material
gs_bapimathead-material    = gwa_itab1-matnr.
*Material details at client data
*material group.
gs_clientdata-matl_group = gwa_itab1-matkl.
gs_clientdatax-matl_group = 'X'.
*Division
gs_clientdata-division = gwa_itab1-spart.
gs_clientdatax-division = 'X'.
*Net Weight
gs_clientdata-net_weight = gwa_itab1-ntgew.
gs_clientdatax-net_weight = 'X'.
*Unit of Weight
gs_clientdata-unit_of_wt = gwa_itab1-gewei.
gs_clientdatax-unit_of_wt = 'X'.
*Base Unit of Measure
gs_clientdata-base_uom = gwa_itab1-meins.
gs_clientdatax-base_uom = 'X'.
endloop.
*calling BAPI for making changes in material and saving thru BAPI.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
    headdata    = gs_bapimathead
    clientdata = gs_clientdata
    clientdatax = gs_clientdatax.
IF sy-subrc NE 0.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
WRITE: / 'Error occured while changing material'.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
WRITE: / 'material',gs_bapimathead-material,'changed'.
ENDIF.

hi hello Guru's
i resolved the issuee..
pleaso go thru the below proram logic for your reference..........
*& Report ZAREPAS36
REPORT zarepas36.
DATA : gs_bapimathead             TYPE bapimathead,
       gs_clientdata              TYPE bapi_mara,
       gs_clientdatax             TYPE bapi_marax.
TYPES : BEGIN OF gty_itab1,
        matnr(18),
        matkl(9),
        spart(2),
        ntgew(13),
        gewei(3),
        meins(3),
        END OF gty_itab1.
DATA : gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
       gwa_itab1 TYPE gty_itab1.
TYPES: BEGIN OF gty_itab2,
       abc(132),
       END OF gty_itab2.
DATA: gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
      gwa_itab2 TYPE gty_itab2.
DATA:ls_return         TYPE bapiret2,
     lt_bapiret2       TYPE standard table of bapiret2.
flat file at selection screen
PARAMETERS: p_files TYPE string.
CALL METHOD cl_gui_frontend_services=>gui_upload
EXPORTING
    filename = p_files
    filetype = 'ASC'
CHANGING
    data_tab = gt_itab2
EXCEPTIONS
    OTHERS   = 8.
LOOP AT gt_itab2 INTO gwa_itab2.
IF gwa_itab2-abc(1) = 'S'.
    gwa_itab1 = gwa_itab2-abc(132).
    APPEND gwa_itab1 TO gt_itab1.
ENDIF.
ENDLOOP.
LOOP AT gt_itab1 INTO gwa_itab1.
*Material
gs_bapimathead-material    = gwa_itab1-matnr.
*Material details at client data
*material group.
gs_clientdata-matl_group = gwa_itab1-matkl.
gs_clientdatax-matl_group = 'X'.
*Division
gs_clientdata-division = gwa_itab1-spart.
gs_clientdatax-division = 'X'.
*Net Weight
gs_clientdata-net_weight = gwa_itab1-ntgew.
gs_clientdatax-net_weight = 'X'.
*Unit of Weight
gs_clientdata-unit_of_wt = gwa_itab1-gewei.
gs_clientdatax-unit_of_wt = 'X'.
*Base Unit of Measure
gs_clientdata-base_uom = gwa_itab1-meins.
gs_clientdatax-base_uom = 'X'.
ENDLOOP.
*calling BAPI for making changes in material and saving thru BAPI.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
    headdata    = gs_bapimathead
    clientdata = gs_clientdata
    clientdatax = gs_clientdatax
IMPORTING
    return      = ls_return.
LOOP AT lt_bapiret2 INTO ls_return.
EXIT.
ENDLOOP.
IF sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
WRITE: / 'Error occured while changing material'.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
WRITE: / 'material',gs_bapimathead-material,'changed'.
ENDIF.

Document Master update - reg

Similar Messages

Maybe you are looking for