PIR are not getting conveter to TLane

[Former Member]

Hi All,

We are facing one issue here and need help.

here we have two ECC system.

E1 and E2 and one APO system.

vendors are mapped to plants of same system or the second ecc system.

we are facing below issue in case vendor is mapped to plant of another system

We have one vendor V1 in E1 ( but mapped to plant exist in E2) and one location L1 in E1 for product P1 in E1.

We have create one purchase info record  PIR1 for the same in E1 system.

When we try to CIF this PIR, system is not creating Tlane and it is not giving any error also.

Please help on this.

Regards,

SA

[rupesh_brahmankar3]

Hello,

Please run the report RIMODINI through SE38 transaction to CIF all the objects again (info-records, plant and vendor).

Also refer KBA 1906011 - Info-Record, Contract or Scheduling Agreement not CIFed to APO

Avoid to use the Source list Integration CIFPUCUST01.

Best Regards,

R.Brahmankar

[Former Member]

Hi,

I think this is tied to BSG. Please check the below explanation.

Also, check this link http://scn.sap.com/thread/3170164

Thanks, Marius

Maintain Business System Group

Use

In this IMG activity, you determine the assignment to a business system group
of this system and the ERP systems that are to be connected. By doing this, you
create areas with the same naming conventions. These guarantee that the same
names are used for master data and also their synchronization in distributed
system landscapes.

Requirements

In addition to the ERP systems, this system too must be assigned to a
business system group (BSG) as an independent logical system.

Example 1

An SCM System is to be connected with the two ERP systems A and B in which

two different materials (for example a hammer and a screw), have the same

material number (100). The two materials are to be represented as two different

products in the SCM system.

Assign The two ERP systems to different BSGs. Assign the SCM system to one of

the two BSGs.

• ERP system A (material number 100 = hammer) -> BSG A
• ERP system A (material number 100 = screw) -> BSG B
• SCM system -> BSG A

In order to avoid having two identical names and to be able to uniquely

assign the material numbers, you also need the Business Add-In (BAdI)

SMOD_APOCF005 for the inbound processing of the product (transaction SE18),

Material number 100 from BSG A is assigned product number 100 in the SCM

system, for example, whereas material number 100 from BSG B gets product number

100_B. In other words, the materials are uniquely assigned.

For master data, the following SAP enhancements are available as BAdIs for

inbound processing in the SCM system:

• Inbound processing of location: BAdI definition SMOD_APOCF001, method
  EXIT_/SAPAPO/SAPLCIF_LOC_001

• Inbound processing of product: BAdI definition SMOD_APOCF005, method
  EXIT_/SAPAPO/SAPLCIF_PROD_001
• For SAP APO only, the following customer exits are available (transaction
  SMOD or CMOD):
  • Inbound processing of resource: APOCF008

• Inbound processing of production process model: APOCF012

Example 2

An SCM System is to be connected with the ERP systems A and B. In the ERP

system A, a certain screw has the material number 110. In the ERP system B,

however, it has the material number 120. Both material numbers are to be mapped

in the SCM system to a product with the product number 110.

Assign the two ERP systems to different BSGs. If possible, assign the SCM

system to the BSG whose data does not have to be renamed.

• ERP system A (material number 110 = screw) -> BSG A

• ERP system B (material number 120 = screw) -> BSG B

• SCM system (product number 110 = screw) -> BSG A

You use the SAP enhancement SMOD_APOCF005 to map the local ERP material
number 120 to the SCM product number 110 in the SCM system.

Note

For the time being, this second scenario is only supported for material
masters and product masters. If, for example, the same customer is used with
different BSGs in ERP systems A & B, you must create two separate customer
locations in the SCM system. This also applies to the vendor, plant, and other
master data.

Message was edited by: Marius Talos

[Former Member]

Hi Marius,

Thanks for your reply,

We have already taken care of thing which you have mentioned.

Product number is same in both the system.

We are planning the same product for different location belonging to both the system in APO.

But this problem arise when we need to plan for one new location.

I don't understand what setting i am missing, because my previous consultant had done this for another location and its working.

Can you help on this.

Regards,

SA

[Former Member]

Hi SA,

Is the new location attached to the same BSG? Also check if they have an user exit to deal with this. If yes, you need to add the new location to it.

Thanks, Marius