Some important definitions in configuration are: The process requires configuration of stock transport orders, inter-company pricing and billing. Stock Transport Order (STO) is a type of purchase order document that posts goods movements in sending and receiving plants while also accounting for receivables and payables in their respective company codes. The offsetting line items from inter-company clearing create a payable in 2000 and a receivable in 1000.Ĭross-company Stock Transfer with shipping and billing The goods receipt posted against the purchase order creates expense in 2000 but liability to pay vendor in 1000.
ASA GNS3 CODE
In example shown, purchase order is in company code 1000 and the assigned cost center 2010 belongs to company code 2000 (other cost objects such as orders can also be used). In this process, a purchase order on a vendor is opened assigning cost center of another entity in the account assignment segment. In the accounting entry, there is a debit to expense account in 2000, a credit to vendor in 1000 and offsetting items inter-company vendor and customer accounts respectively. In the example shown below, company code 1000 is posting a vendor invoice for an expense incurred in company code 2000. Cross-company code transaction in FIĬross-company code transaction (viewed from transaction code FBU3) is an accounting entry involving more than one company code. The company codes used share the same controlling area in these examples. Sensitive information had to be masked on screenshots. The document may not be comprehensive, uses simple & basic examples. The document is not describing detailed configuration behind these transactions or any valuations such as transfer pricing. This is a high-level document that shows some cross company and inter-company postings. Many inter-company transactions may occur between difference entities (company codes) and SAP implementation should support such transactions and valuations. These company codes could be establishments in different geographies, countries or could be related parties or affiliates operating at different levels of integration of supply chain (to give some examples). Each legal entity could be a separate company code in SAP organization structure. This is just the very basic config, since we don't know what (if any) routing is in place in your network.įailover interface ip FAILOVER 10.67.14.65 255.255.255.252 standby 10.67.14.To manage a complex business, often corporates incorporate multiple legal entities. Type echo protocol ipIcmpEcho 192.168.1.1 interface outsideĪction 2.0 cli command "interface GigabitEthernet0/0" On the ASA1, you would configure this (one script for when the interface is down, one script for when it is up): Let's say the IP address of the uplink interface on the ASA1 that is connected to R1 is 192.168.1.1/30. What criteria do you want the failover to be triggered by ? If you want it to be triggered by let's say by the failure of the uplink to the router (R1), the IP address of that interface is what you monitor, and when it it not reachable, an EEM script will execute. So you have to get creative, and you could use sla monitoring and EEM scripts to trigger the failover. The typical active/standby failover setup indeed involves logical L2 connectivity, which you don't have (as far as I can tell from your description). Ip address 192.168.30.1 255.255.255.0 standby 192.168.30.254įailover lan interface FAILOVER GigabitEthernet0/0įailover interface ip FAILOVER 10.67.14.65 255.255.255.252 standby 10.67.14.66įailover link FAILOVER GigabitEthernet0/0ĭescription Downlink to GigabitEthernet0/2 ASA1ĭescription Downlink to GigabitEthernet0/2 ASA2ĭescription Uplink to GigabitEthernet0/1 ASA1ĭescription Uplink to GigabitEthernet0/1 ASA2
Here are the working configs (IP addressing an interfaces used are obviously arbitrary, make sure they match what you actually have configured):ĭescription Link to GigabitEthernet0/0 Novi_Core_10 I labbed this up, and ended up using a bridge group for the router.
0 kommentar(er)
