Default Intercompany rule
Hi Guys
I have few IC accounts and all have the same PlugAcct. I have the balances of these accounts from TB. Is there any default rule for the eliminations? If yes then can you please let me know?
Thanks!
If you didnt set content tab that would be default aggregation, means based on the columns pull in the criteria SUM changes like drill down or roll up.
'Group by' clause keep on changes as per the column in the criteria.
When you set any level for a metric then it alway aggregated to that level, values will not change as per column selection.
Pls mark if helps
Edited by: Srini VEERAVALLI on Nov 1, 2012 4:48 AM
Any updates on this?
Edited by: Srini VEERAVALLI on Jan 7, 2013 1:56 PM
Similar Messages
-
Default Business Rules at AppSet level
Hi Experts,
Once you create a new AppSet by copying AppShell and add a "Consolidation" type application with all business rules, a default "Business Rules Library" is generated at AppSet level along with "Business Rule" within Application. The "Business Rules Library" at AppSet level includes "Consolidation Rules" and "Consolidation Methods". In my BPC 7.5 MS SP04 these default business rules table is empty, whereas it used to come with values pre-filled in it in earlier versions. I discussed this with one of the BPC NW consultant and he confirmed that for BPC 7.5 NW this issue was there that those values were there on backend but was not visible from the frontend Admin Console. After applying some patch in BPC 7.5 NW, it becomes visible in Admin Console Business Rules Library at AppSet level.
Can anybody using BPC 7.5 MS version confirm whether they are getting these values by default or they are entering it manually.
Edited by: Amitkumar Shyamanand on Jan 25, 2011 11:18 AMYou may need to confirm with SAP Support, but I beleive that the latest versions of 7.5 on Microsoft has a very slimmed down version of AppShell, and that the business rules are not included in the process. Best if you get an Appshell from version 7 and create you copy which will then have all the Appset Business RUles.
Hope this helps. -
Default settlement rule with settlement type as FUL for service orders
Hi Folks,
Could you please advise me on the below issue?
Requirement: setting up of default settlement rule with default settlement receiver as u201CCOST CENTREu201D and settlement type as u201CFULu201D for the maintenance orders (Order category u2013 30).
I was trying to configure the same in transaction KSR3_ORI to assign the strategy to the service order type by clicking u201CNew Entriesu201D system not showing the drop list for the status column which is a mandatory field.
We have applied the below notes:
Note 313454 - Info: Default value for settlement type
Note 851975 - Settlement use automatic generation creates
Could you please guide us to get the default settlement rule for service orders along with settlement type as u201CFULu201DI was also with this problem in 2013 january and only found some information about this, here.
Our solution was change the Maximum number of distribution rules in Maintain Settlement Profiles to 1, because we wanted the FUL rule and it is always in the first line.
Now, for curiosity, I was search for another solution and found the SAP note 2028108 that explain that is not possible to change the strategy for PM/CS orders.
This note was released at 09.06.2014 -
How to set the default settment rule for the same kind project.
hi experts:
the project of the same kind of the project profile have the same settment rule to one account (G/L).
how to set the default settment rule for the project of this kind of the project profile.
regardsHi,
You need to define the settlement profile and allocation structure.
next you need to define the Strategy for settlement rule.
navigation-PS> costs> automatic and periodic allocations> settlement> Settlement rule for WBS
--> Define strategy for settlement rule.
Select the strategy and click on settings. in that new entries, check the Acc Assg element, enter Settlement profile and mention accass category as reposnsible cost center.
Save this transaction.
Now create a project assgin responsible costcenter for the WBS element in the project buider and save the transaction.
Now run CJB2 transaction for the project, settlement rule will generated automatically.
even you can configure the same for profitability segment.
Rgds
Sudhir Reddy -
Can someone explain me as to how BI interprets the default aggregation rule.
Say when we say the defualt aggregation rule on the sales fact table column revenue is SUM. what does it actually imply.
Similarly when we use the Aggregation Content tab in the Logical table source and set aggregation content group by what does it actually mean.
Thanks,
ChanIf you didnt set content tab that would be default aggregation, means based on the columns pull in the criteria SUM changes like drill down or roll up.
'Group by' clause keep on changes as per the column in the criteria.
When you set any level for a metric then it alway aggregated to that level, values will not change as per column selection.
Pls mark if helps
Edited by: Srini VEERAVALLI on Nov 1, 2012 4:48 AM
Any updates on this?
Edited by: Srini VEERAVALLI on Jan 7, 2013 1:56 PM -
Default Settlement Rule of PM Maintenance Order
Hi,
While creation of settlement rule on Maintenance Order, Option appears of default settlement rule. Whenever i select that option on Settlement Rule definition screen, two rows appears for the same Cost reciever automatically ( One for Full settlement and second for Periodical Settlement) But i only want Full settlement option to appear on screen in this scenario. Can anybody pin point the root cause and share the solution of it.hi
while defining the settlement profile specify CTR as default settlement receiver and check ,and also make the settlement profile mandatory for order release,
regards
thyagarajan -
Hi, RVS4000 has default firewall rule from ANY WAN -> to ANY LAN with status Allowed. Should that be denied by default, like in RV042 or RVL200?
Jasbryan,
Thank you for suggesting the call to business support.
The support staff member was able to fully clarify (and thus resolve) the issue. Further, she will initiate the steps necessary to get the GUI updated in a future firmware release, so that the default rule will properly reflect DENY for all WAN to LAN connections.
And so that others might be made aware (or learn, as did I) about the operation of the RV4000 firewall, here is a brief description of the resolution. Being used to One-To-One NAT devices, I believed that in addition to a Port Forwarding rule, I also needed to create a corresponding ACL firewall rule. However the support agent revealed that a Port Forwarding entry (automatically) opened the appropriate port(s) in the firewall, so that creation of an explicit rule was not necessary. My testing that revealed open ports without the presence of an ACL had only been done on ports associated with my Port Forwarding rules, so my testing was basically flawed. Now I know! -
Default Settlement Rule for Project Definition
Hi Viewers,
I am having the requirement that, when i create the project, automatically system should create the AUC asset in the project level.
I tried and I am able to make at WBS element level. I need at Project level.
I need help on this...
Regards,
AswinHello,
In Customizing for the order type it is set that orders should be settled periodically (default rule PP2). However, this is not supported for subordinate orders in the collective order.
For this collective order, the system sets the default rule to PP1 regardless of the settings predefined in the order type. Then the collective order is subject to full settlement.
200060 - Periodic settlement in the collective order
Please check if you have any custom development for settlement.
If not then raise this to OSS.
Best Regards,
R.Brahmankar -
Hi All,
Billing Type ZNIV (Copy of IV) should be the default billing type when I craate Inter Company Invoice (Purchase Order - Delivery - Inter Company Scenario).
In sales we can assign ZNIV document type to Order types so that ZNIV will be defaulted at the time od Inter comp invoice creation.
Same scenario If i create a Purchase Order and delivery, defaulted billing doc type is IV actually it should be ZNIV.
Where can I link ZNIV document type to PO or Delivery?Hi,
To solve this issue you need to maintain two seetings
1.Maintain intercompany billing type in Sales order controls (VOV8) :- which you already have done
2.Maintain copy control in Delivery to Billing copy control in Tcode VTFL.
Here you can copy the exsisting standard copy control for LF to IV and change the billing type to your ZNIV billing type.
So whenever you will create the billing as per VOV8 and VTFL settings ZVIN will be defaulted.
Reward points if useful
Regards,
Amrish Purohit -
PL/SQL API + Defaulting Rules in OM
Hi,
I want to default custom rule in Sales Order from whenever I select Item. After selecting item from the sales order from, it should populate Warehouse value in Shipping tab. I am using custom PL/SQL API option. I wrote one function and kept in package. I was disabled all defaulting rules. Now If I select Item in sales order form, I am not getting warehouse value.
The steps are:
Step 1. Select Warehouse attribute and define defaulting rule
Application: Order Management
Entry: Order Line
Select Attribute as Warehouse
Click on Defaulting Rules
Step 2: Define Defaulting Sourcing Rule
Select Source type as PL/SQL API.
In the Defaulting Source/Value field give Package Name and Function Name.
Open Catalog Groups window from the below path: Setup Items Catalog Groups
Specify Name and Description for Catalog Group
Click on Details button.
Step 3: Create Catalog Group
Step 4: Specify Descriptive Elements for the Item Catalog Group
Step 5: Code preparation
-- My Custom Code
Create or replace FUNCTION custom_default_rule
RETURN VARCHAR2
AS
l_line_type_rec oe_order_cache.line_type_rec_type;
CURSOR cus_l
IS
SELECT a.organization_code, b.element_name, b.element_value
FROM mtl_parameters a,
mtl_descr_element_values b,
mtl_system_items_b c
WHERE b.inventory_item_id = c.inventory_item_id
AND a.organization_id = c.organization_id
AND a.organization_id = c.organization_id
AND c.inventory_item_id = 12924
GROUP BY a.organization_code, b.element_name, b.element_value
ORDER BY a.organization_code, b.element_name, b.element_value;
BEGIN
l_line_type_rec := oe_order_cache.load_line_type
(ont_line_def_hdlr.g_record.line_type_id);
FOR cur_rec IN cus_l
LOOP
IF cur_rec.element_name IN
('Frequency',
'Emission Norms',
'Voltage',
'Duty Rating',
'Phase',
'Product'
AND cur_rec.element_value IN
('50', '', '230', 'Medium', 'Single', 'QSK60')
THEN
RETURN cur_rec.organization_code;
ELSIF cur_rec.element_name IN
('Frequency',
'Emission Norms',
'Voltage',
'Duty Rating',
'Phase',
'Product'
AND cur_rec.element_value IN
('50', '', '230', 'Medium', 'Three', 'QSK15')
THEN
RETURN cur_rec.organization_code;
ELSIF cur_rec.element_name IN
('Frequency',
'Emission Norms',
'Voltage',
'Duty Rating',
'Phase',
'Productfamily'
AND cur_rec.element_value IN
('50', '', '230', 'Medium', 'Single', 'DQK50')
THEN
RETURN cur_rec.organization_code;
END IF;
END LOOP;
EXCEPTION
WHEN OTHERS
THEN
IF oe_msg_pub.check_msg_level (oe_msg_pub.g_msg_lvl_unexp_error)
THEN
oe_msg_pub.add_exc_msg ('OE_Default_PVT', 'CUSTOM_DEFAULT_RULE');
END IF;
RAISE fnd_api.g_exc_unexpected_error;
END custom_default_rule;
Step 6: Create a Sales Order (Order Returns Sales Orders)
Select Customer and Order Type and select Line Items Tab.
Select Item from the Ordered Item Field. Press Tab.
After pressing tab in the Shipping Tab Warehouse value Should be populated. But it is not working.
Can anyone guide me in this.
It is very urgent.
If possible, Please send u r details to my official id: [email protected]
Thanks in Advance,
sateeshSateesh,
This is working fine for me here:
CREATE OR REPLACE PACKAGE xx_def_wh
AS
FUNCTION custom_default_rule (p_database_object_name IN VARCHAR2, p_attribute_code IN VARCHAR2)
RETURN NUMBER;
END;
CREATE OR REPLACE PACKAGE BODY xx_def_wh
AS
FUNCTION custom_default_rule (p_database_object_name IN VARCHAR2, p_attribute_code IN VARCHAR2)
RETURN NUMBER
AS
l_line_type_rec oe_order_cache.line_type_rec_type;
l_item_id NUMBER;
CURSOR cus_l(p_item_id in number)
IS
SELECT a.organization_id, b.element_name, b.element_value
FROM mtl_parameters a, mtl_descr_element_values b, mtl_system_items_b c
WHERE b.inventory_item_id = c.inventory_item_id
AND a.organization_id = c.organization_id
AND a.organization_id = c.organization_id
AND c.inventory_item_id = p_item_id
and a.organization_id<>a.master_organization_id
ORDER BY a.organization_id;
BEGIN
l_line_type_rec := oe_order_cache.load_line_type (ont_line_def_hdlr.g_record.line_type_id);
l_item_id:= ONT_LINE_DEF_HDLR.g_record.inventory_item_id;
FOR cur_rec IN cus_l(l_item_id)
LOOP
IF cur_rec.element_name IN ('Frequency', 'Emission Norms', 'Voltage', 'Duty Rating', 'Phase', 'Product')
AND cur_rec.element_value IN ('50', '', '230', 'Medium', 'Single', 'QSK60')
THEN
RETURN cur_rec.organization_id;
ELSIF cur_rec.element_name IN ('Frequency', 'Emission Norms', 'Voltage', 'Duty Rating', 'Phase', 'Product')
AND cur_rec.element_value IN ('50', '', '230', 'Medium', 'Three', 'QSK15')
THEN
RETURN cur_rec.organization_id;
ELSIF cur_rec.element_name IN ('Frequency', 'Emission Norms', 'Voltage', 'Duty Rating', 'Phase', 'Productfamily')
AND cur_rec.element_value IN ('50', '', '230', 'Medium', 'Single', 'DQK50')
THEN
RETURN cur_rec.organization_id;
END IF;
END LOOP;
EXCEPTION
WHEN OTHERS
THEN
IF oe_msg_pub.check_msg_level (oe_msg_pub.g_msg_lvl_unexp_error)
THEN
oe_msg_pub.add_exc_msg ('OE_Default_PVT', 'CUSTOM_DEFAULT_RULE');
END IF;
RAISE fnd_api.g_exc_unexpected_error;
END custom_default_rule;
END;
Thanks
Nagamohan -
Re: cProject settlement rule defaulting as PSG during transfer.
Hello
We currrently use multi-level controlling scenario for cProjects, which generates project and subsequent WBS elements automatically.
I am looking at using automatic generation of settlement rules on all WBS elements to default 'CTR' and have created a settlement profile and strategy to incorporate this. The set.profile has been defautled in the project profile in PS and also in the Maintenance for cProjects Controlling scenario config within Accounting integration.
However, every time I transfer the cProject to PS, an error message in the controlling cockpit states 'Receiver categ. 'PSG' is not allowed by settlement rule' - which is correct as I have configured the profile for CTR only.
Is there t-code to access the cProject's defaulted settlement rule so it can changed to CTR and not PSG?
I have checked IAOM0 and doesn't seem to be there.
Thanks
PabloHi Pablo,
I see you encountered this error in 2009 and it hasn't been marked as answered yet.
I was wondering if you found any solution on this one later, because we are facing the same exact error in our current project. I would really appreciate if you share any info. on it.
Thanks,
DHP -
What is the Difference between Checking Rule B and RP
Hi Experts,
Can anybody Explain the Difference between Checking Rule B and RP
in Intercompany STO (between Company Codes) which one should i be use?
in standard settings of IDES system i found B assigned to PO Type NB. but somewhere in forum i saw checking rule RP to be assigned to NB. i totally confused. please help me.
In below Assignments which one is correct.........
NB (PO Type) - 1200 (Supplying Plant) - NLCC (Delivery Type) - B (Checking Rule)
NB (PO Type) - 1200 (Supplying Plant) - NLCC (Delivery Type) - RP (Checking Rule)
Thanks in Advance,
charysd
Edited by: charysd on Aug 2, 2011 12:32 PMhi..
By default checking rule B is assigned to PO doc type...
In B...only delivery rule is considered..
while in RP..delivery time..lead time...transpotation time are added..
Hope it will help.
Thnks. -
ASA 5505 NAT rules blocking inside traffic
Previous attempts to set up these NAT rules has been met with minimal success. We have been able to get the NAT rules created, and able to ping our inside servers and receivers from a different outside network, but every time we get that far our internal network crashes. Running the Packet Trace utility via the ASDM shows that internal traffic from the servers to the workstations is being blocked by the default implicit rule under the access rule heading that states "any to any, service being ip, action= deny". Reverse traffic from the workstations to the servers is being allowed though. In an effort to start over again, the Cisco ASA has been Factory Defaulted via the CLI, and has had it's Inside network, and Outside IP address set back up. DHCP pool has been setup for a minimal amount of addresses on the inside network, since most of our equipment will always be assigned statics. We reset our static NAT policies, and seem to be having the same problem. My partner and I have been working on this for some time now, and have ourselves so frustrated that I know we are missing something simple. Any help will be greatly appreciated.
Embarq : Network xxx.xxx.180.104
Gateway: xxx.xxx.180.105
Subnet Mask: 255.255.255.248
Our Static IP's: xxx.xxx.180.106 to xxx.xxx.180.110
Cisco Pix for VPN tunnels : xxx.xxx.180.107 outside IP
used for DataBase Servers : 100.1.0.2 Inside IP/ Gateway 2
Cisco ASA 5505: xxx.xxx.180.106 outside IP
all other traffic : 100.1.0.1 Inside IP/ Gateway 1
Inside Network: 100.1.0.0/24
Application Server: 100.1.0.115 uses Gateway 1
BackUp AppSrvr: 100.1.0.116 uses Gateway 1
DataBase Server: 100.1.0.113 uses Gateway 2
BackUp DBSrvr: 100.1.0.114 uses Gateway 2
Cobox/Receiver: 100.1.0.140
BackUp Cobox: 100.1.0.150
Workstation 1: 100.1.0.112
Workstation 2: 100.1.0.111
Network Speaker1,2,3,4: 100.1.0.125 to 100.1.0.128
Future Workstations: 100.1.0.0/24
1. Embarq Gateway feeds both Cisco Pix, and Cisco ASA. Both Ciscos feed a Dell Switch.
2. All inside network devices at 100.1.0.0/24 are networked into the Dell Switch.
3. All Workstations/Network Speakers need to be able to communicate with all four servers, and the Cobox/Receiver.
4. The DataBase Servers have VPN tunnels created in the Pix for clients to be able to login securely and edit their account info.
5. The App Server (100.1.0.115), and BackUp App Srvr (100.1.0.116) need to have a NAT rule created NAT'ing them to xxx.xxx.180.109.
A. The xxx.xxx.180.109 NAT rule needs to allow ALL UPD traffic TO and FROM ANY outside IP address.
B. The xxx.xxx.180.109 NAT rule needs to allow ICMP traffic FROM ANY Outside IP address.
6. The Cobox/Receiver (100.1.0.140) and BackUp Cobox (100.1.0.150) need to have a NAT rule created NAT'ing them to xxx.xxx.180.108
A. The xxx.xxx.180.108 NAT rule needs to allow UDP traffic FROM ANY Outside IP address source port 6000 or 9000 to destination port 9000
B. The xxx.xxx.180.108 NAT rule needs to allow ICMP traffic FROM ANY Outside IP address.
7. Right now the Cisco PIX is functioning and working perfectly for our VPN tunnels.
8.
: Saved
ASA Version 8.2(5)
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
interface Ethernet0/0
switchport access vlan 2
interface Ethernet0/1
interface Ethernet0/2
interface Ethernet0/3
interface Ethernet0/4
interface Ethernet0/5
interface Ethernet0/6
interface Ethernet0/7
interface Vlan1
nameif inside
security-level 100
ip address 100.1.0.1 255.255.255.0
interface Vlan2
nameif outside
security-level 0
ip address xxx.xxx.180.106 255.255.255.248
ftp mode passive
same-security-traffic permit intra-interface
object-group protocol DM_INLINE_PROTOCOL_2
protocol-object ip
protocol-object icmp
protocol-object udp
protocol-object tcp
object-group protocol DM_INLINE_PROTOCOL_1
protocol-object ip
protocol-object icmp
protocol-object udp
protocol-object tcp
object-group protocol DM_INLINE_PROTOCOL_3
protocol-object ip
protocol-object icmp
protocol-object udp
protocol-object tcp
object-group protocol DM_INLINE_PROTOCOL_4
protocol-object icmp
protocol-object udp
object-group protocol DM_INLINE_PROTOCOL_5
protocol-object icmp
protocol-object udp
access-list outside_access_in extended permit object-group DM_INLINE_PROTOCOL_3 any xxx.xxx.180.104 255.255.255.248
access-list outside_access_in extended permit object-group DM_INLINE_PROTOCOL_4 host xxx.xxx.180.108 any
access-list outside_access_in extended permit object-group DM_INLINE_PROTOCOL_5 host xxx.xxx.180.108 any
access-list inside_access_allow extended permit object-group DM_INLINE_PROTOCOL_2 100.1.0.0 255.255.255.0 100.1.0.0 255.255.255.0
access-list inside_access_allow extended permit object-group DM_INLINE_PROTOCOL_1 any any
access-list inside_nat_static extended permit udp host 100.1.0.140 eq 9000 any
access-list inside_nat_static_1 extended permit ip host 100.1.0.115 any
access-list inside_nat0_outbound extended permit ip 100.1.0.0 255.255.255.0 100.1.0.0 255.255.255.0
access-list outside_nat_static extended permit udp host xxx.xxx.180.108 eq 6000 host 100.1.0.140
access-list outside_nat_static_1 extended permit ip host xxx.xxx.180.109 host 100.1.0.115
pager lines 24
logging asdm informational
mtu inside 1500
mtu outside 1500
icmp unreachable rate-limit 1 burst-size 1
icmp permit any outside
no asdm history enable
arp timeout 14400
nat-control
global (inside) 1 100.1.0.3-100.1.0.254 netmask 255.0.0.0
nat (inside) 0 access-list inside_nat0_outbound
static (inside,outside) udp xxx.xxx.180.108 6000 access-list inside_nat_static
static (outside,inside) udp 100.1.0.140 9000 access-list outside_nat_static
static (inside,outside) xxx.xxx.180.109 access-list inside_nat_static_1
static (outside,inside) 100.1.0.115 access-list outside_nat_static_1
access-group outside_access_in in interface outside
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 192.168.1.0 255.255.255.0 inside
http 100.1.0.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 6ecc7aa5a7032009b8cebcf4e952d491
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
dhcpd address 100.1.0.5-100.1.0.15 inside
dhcpd dns 71.0.1.211 67.235.59.242 interface inside
dhcpd auto_config outside interface inside
dhcpd enable inside
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
prompt hostname context
call-home reporting anonymous
Cryptochecksum:52e69fa95fcffd43ed9e73df320e3a55
: end
no asdm history enableOK. Thank you very much for your help. I am going to get with the powers that be to upgrade the "Base" license in this ASA.
In the meantime I will Close and Rate this post for now so others can get this info also.
If we have any further issues after the upgrade, then I will open a new post.
Thanks again. We new it was something simple. Not sure how we overlooked that, but hey we're getting somewhere now. -
Settlement Rule for Internal Order
Hi All
I have Maintained Settlement rule for Internal order as under
CAT - FXA
Settlement Receiver - Asset
% - 100
Settlement type - Full
Now after settlement of above Order in KO88 . I want again use above internal order. Hence i have trying to put Settlement rule 50% for some anther asset but system gave me following error. Please guide on this issue.
Total = 50.00%, ( Set.Type PER / Version / Actual settlement ), period 010/2011
Message no. KD042
Diagnosis
You have entered distribution rules which settle 50.00% in total. This applies for settlement view ( Set.Type PER / Version / Actual settlement ) in period 010/2011.
When checking the percentage total, the system found one of the following errors:
The total percentage for the distribution rules is more than 100%
The total percentage for the distribution rules is less than 100% and this is a rule for full settlement.
The total percentage for the distribution rules is less than 100% and the 100% check is switched on in the settlement profile.Hi:
Please refer to the contents of OSS Note 45612 - IM: pre-settlement does not work, or KD042... which states
"Symptom
1. If a preliminary settlement rule (for example, to cost center) is entered for individual items of capital investment measures with line item management, this rule is not considered during periodic settlement. There is no settlement to cost centers.
2. If you enter a final settlement rule for individual line items of investment measures with line item management for a partial capitalization (that is, the percentage rate is less than 100%), then you receive the unjustified error message KD042 "Total percent = xx%".
Additional key words
KOB5, CJ70, CJ88, CJ8G, KO88, KO8G, preliminary settlement, partial settlement, partial capitalization
Cause and prerequisites
1. You did not enter the settlement type ACT in the preliminary settlement rule.
You can check this in the Line Item Apportionment transaction by choosing the menu option "Goto" -> "Overview dist. rules" to display the distribution rule groups entered so far.
The system displays rules which have no entry in the "SetTyp" field (settlement type, field name PERBZ).
2. The check of the percentages is incorrect.
Solution
1. Install the following correction. Afterwards reverse the incorrect settlement, re-enter the preliminary settlement rule and settle again.
2. Install the following correction. Afterwards, you can maintain the settlement rule for the partial settlement.
Note: If you want to use a default settlement rule (maintaining the settlement rule from the master data maintenance transaction), then you are required to distribute the line items at 100%. In order to carry out a partial capitalization (settlement of less than 100%), you have to use menu path "Actual postings -> Period-end closing -> Settlement -> Line item "
Regards -
Doubt about the settlement rule of the Production ORder
The only default distribution rule allowed for a PP order is PP1 or PP2. We would need to change that to allow settlement to multiple receivers as a default. If that is the case, we may want to look into a user exit to update the settlement rule during production order creation instead so that the G/L account is correct from the beginning.
Currently when we create the production order, the settlement rule will default the below, I am not sure if a user exit is able to maintain the Source as 200 (Materials)?
If yes, we can then add the second rule for Source 100 (Labor and Mfg) via the user exit as well.
In this case, SAP will not prompt us error of settlement with 200%, as they are from difference Sources.
now anybody can explain me about the User EXit we have to correct thisany help on this.. please its very urgent
thanks in advance
Maybe you are looking for
-
I get a black screen on the camera app on my iPod touch? Is there a solution? Resetting only helped for a few days, the problem comes back. Camera works, with the side buttons it takes pictures. Although I'm not able to see on the screen. Mike
-
How can I use iWeb to create website that contains a lot of downloadable audio files?
Hi How to use iWeb to create a website that contains a downloadable audio files. I'm uloading about 15 GB of audio files. I need to creat folders "albums" and then put the files in these folders. Any advise? Thank you very much for your time to t
-
Is Asynchronous ABAP proxy client possible without XI ?
Hi there, Does anyone of you know if it is possible to create an asynchronous ABAP proxy client, without XI, thus directly in a SAP ERP 60 ABAP ? Karim
-
Corrupted Time Machine file?
Have 2 MacBook Pro's on a network with Time Capsule, both were working fine until about 5 days ago when one would hang when trying to back up. I suspect a file problem, but when I try disk repair on the sparsebundle file the disk utility hangs. I tri
-
Where's the CiscoSecure ACS agent
I am implementing a ACS 1111 Cisco Secure ACS Appliance and am trying to find the agents that are needed for the windows workstations to authenticate thru it. I cannot find anything that isn't 3 years old and only for 95/NT. I know there's got to be