cancel
Showing results for 
Search instead for 
Did you mean: 

Specification of "Stand alone" at SRM7.03

Former Member
0 Kudos

Could you please confirm below question.

Regarding replicatiion of vendor master at "Stand alone scenario",

only ERP vendor master which does not have
purchasing view can be  transported from ERP to SRM?

Some current ERP vendor masters are used
for only FI, not subject to purchasing

(These vendors do not have purchaing view).

And we would like to use the existence of purchasing view for

determinating what vendors will be
transported from ERP to SRM.

    

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member216093
Contributor
0 Kudos

Hi Tetsuo,

Purchasing view of the vendor contains vendor currency, PORG and other details which are mandatory in ECC and in SRM system to complete the transaction and to create the PO out of approved SC.

If there is no purchasing view there is no point of replicating the vendor into SRM as it can not connect to any PORG. I believe that these points have been given proper thought.

I am not questioning the design but just raising these points for you to rethink.

We have actually done developments which are matching with your requirements.

1) Put a purchasing block on the vendors which don't have purchasing views implement BADI VENDOR_ADD_DATA

2) If the vendor is blocked it will not be picked for replication.

Regards,

Ravi

Former Member
0 Kudos

Hi Ravi.

Thanks for your prompt response.

Your concrete advise really help me to

consider the principle of the replication of our customer.

Best Regard.

Tetsuo

former_member216093
Contributor
0 Kudos

This message was moderated.

Former Member
0 Kudos

Hi Ravi.

Our corresponding principle became below at this time.

- Two purchase organizations are defined at SRM for backend and local.

- Only vendor masters of ECC that are linked to purchase organization of

  backend system defined at SRMwould be replicated.

- After replication, local purchase organization whould be allicated to each vendor master.

  (Using BBP_UPDATE_PROG)

The principle of maintainance of vendor(only for purchasing) became below.

- Register Vendor master at ECC (General data,Porg dat,Company data)

- Replicate to SRM(BBPGETVD)

- Allicate local purchasing organization to SRM(BBP_UPDATE_PROG)

The principle of maintainance of payee

(only for paying, not used at purchasing) became below.

This is my first contribution, and

I think my setting currently cannot give point.(Icon for giving points is not displayed)

I apologize so much for not being able to give points to you.

Best Regard.

Tetsuo

former_member216093
Contributor
0 Kudos

Hi Tetsuo,

It looks like you are setting up extended classic scenario of SRM and need local and backend entities. In this scenario, you need to maintain the cross responsibilities for PORG and PRGPs so that when the SC is created using local entities, the corresponding backend entities are also identified correctly.

As the local and backend PORGs will have cross responsibilities, the vendor shall be replicated to corresponding local PORG once it is available in backend PORG.

Regards,

Ravi